Re: What's cooking in git.git (Dec 2015, #03; Thu, 10)

From: Stefan Beller <sbeller@google.com>
Date: Dec 10, 2015, 23:55 UTC
Message-ID: <CAGZ79kY8M-Xv1s4-s7HnjxZ_X19SR4PsWMtQ3yogqN=vjDiMwQ@mail.gmail.com>
In-Reply-To: <xmqqvb85g8v9.fsf@gitster.mtv.corp.google.com>

On Thu, Dec 10, 2015 at 3:51 PM, Junio C Hamano <gitster@pobox.com> wrote:

Show 16 quoted lines

> Stefan Beller <sbeller@google.com> writes:
>
>>> * sb/submodule-parallel-fetch (2015-11-24) 17 commits
>>> ...
>>
>> I assume you plan on merging this after 2.7 settled and then we can
>> also get the above sb/submodule-parallel-update going again.
>
> Yeah, thanks for reminding me.  I think that would be a good plan
> that gives us an opportunity to clean up this topic, some parts of
> which are have "an early patch that was too hastily merged to 'next'
> had to be tweaked by an 'oops' follow-up patch in the topic"
> pattern, e.g. "make waitpid the secondary and closed pipe the
> primary way to monitor children".
>
> Thanks.

This makes it sound as if you would drop it from next once 2.7 is out, expecting a complete reroll, which does the right thing from the beginning? That was not was I was expecting, but thanks for clarifying.