Junio C Hamano <gitster@xxxxxxxxx> writes: > The only reason a topic is queued in 'pu' is to let me not pay > attention to it, without risking to forget about it completely ;-). > > The topics on 'pu' have potential to be a useful change even though > they are far from ready for 'next'. That's not "even though" but should have been "even when". Sometimes when I feel a topic is already of 'next' quality, the author suggests that a reroll is coming, and I hold such a topic off. Also, inverse is not true, as always. Some topics may not be queued in 'pu' when I push a day's integration results out, but that does not mean they do not have potential to be useful. They may not be in 'pu' because I didn't have enough time to get around to them, or because there was discussion ongoing and I saw the author was actively responding to the comments, relieving me from having to keep an eye on the topic at all until the dust settled without even queueing it on 'pu'. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html