Re: What's cooking in git.git (Sep 2017, #03; Fri, 15)
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Sep 15, 2017, 20:49 UTC
- Message-ID
- <xmqqfubnwuuz.fsf@gitster.mtv.corp.google.com>
- In-Reply-To
- <alpine.DEB.2.21.1.1709152122360.219280@virtualbox>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Show 34 quoted lines
> Hi Junio, > > On Fri, 15 Sep 2017, Junio C Hamano wrote: > >> -------------------------------------------------- >> [Cooking] >> >> [...] >> >> * mk/diff-delta-uint-may-be-shorter-than-ulong (2017-08-10) 1 commit >> ... >> Dropped, as it was rerolled for review as part of a larger series. >> cf. <1502914591-26215-1-git-send-email-martin@mail.zuhause> >> >> [...] >> >> * mk/use-size-t-in-zlib (2017-08-10) 1 commit >> ... >> Dropped, as it was rerolled for review as part of a larger series. >> cf. <1502914591-26215-1-git-send-email-martin@mail.zuhause> >> >> >> * mk/diff-delta-avoid-large-offset (2017-08-11) 1 commit >> ... >> Dropped, as it was rerolled for review as part of a larger series. >> cf. <1502914591-26215-1-git-send-email-martin@mail.zuhause> >> >> >> -------------------------------------------------- >> [Discarded] >> >> [...] > > These three topics are still in the wrong category. Please fix.
Hmph, but did the larger series these refer to actually land? If I recall correctly they were too invasive to get merged cleanly to 'next' and 'pu' without disrupting topics in flight and that is why it is not even listed there.
The only two reasons a topic with a good goal and approach gets thrown into the Discarded bin are either because it is tentatively retracted to avoid disrupting other topics in flight (with the expectation to be redone later) or what it wants to solve is addressed by another topic and becomes unnecessary.
These three attempt to do good things and I have been hoping that others can help moving them forward by e.g. reporting that they still cleanly merge and stand on their own as improvements at a smaller scale than the larger one that was attempted but was not queued, or if nobody volunteers, I was guessing that I might end up doing that myself. Before that happens, I'd prefer to keep them listed and topics kept in my tree, even if they are not part of 'pu'.
On the other hand, because many topics have graduated to master recently, the larger one (possibly in the updated form---I do not recall what conflicts it had with what other topics) may be able to cook peacefully together with topics we have that are still in flight. If that is the case, then that larger topic will be queued and these three will truly become material for the Discarded bin.