Re: What's cooking in git.git (Dec 2018, #01; Sun, 9)

From: Junio C Hamano <gitster@pobox.com>
Date: Dec 11, 2018, 01:48 UTC
Message-ID: <xmqqsgz4n89k.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <CABPp-BGVHnaZLg4fuptVmNa=jRHg0cMDTWjv1NdLQJXPe=+ahw@mail.gmail.com>

Elijah Newren <newren@gmail.com> writes:

Show 10 quoted lines

> On Sun, Dec 9, 2018 at 12:42 AM Junio C Hamano <gitster@pobox.com> wrote:
>
>> Git 2.20 has been tagged.  I'd expect that we would slow down to see
>> how stable it is and queue only the brown-paper-bag fixes for a week
>> or so, before opening the tree for the next cycle, rewinding the tip
>> of 'next', etc.
>
> Does this mean you'd prefer we continue to wait a little longer before
> sending in new series and re-rolls, or just that you are managing
> expectations about when they might be queued?

More of the latter. The best way to find bugs that matter in real life is to use the software in the real project settings, i.e. you guys work on your own topics using Git. I'll keep reviewing and commenting just like other reviewers, but the new patches won't come close to 'next' (as I said elsewhere, being in 'pu' does not count much---it is like getting bookmarked) in the meantime.