Re: What's cooking in git.git (May 2020, #08; Sun, 24)

From: Junio C Hamano <gitster@pobox.com>
Date: May 25, 2020, 16:22 UTC
Message-ID: <xmqqd06sougm.fsf@gitster.c.googlers.com>
In-Reply-To: <CABPp-BHxeDQS5QXd5Sf6Ws_58-aze_mes3xRvGZYQNWw3Et3VA@mail.gmail.com>

Elijah Newren <newren@gmail.com> writes:

Show 19 quoted lines

> On Sun, May 24, 2020 at 8:35 PM Junio C Hamano <gitster@pobox.com> wrote:
>>
>> Here are the topics that have been cooking.  Commits prefixed with
>> '-' are only in 'pu' (proposed updates) while commits prefixed with
>> '+' are in 'next'.  The ones marked with '.' do not appear in any of
>> the integration branches, but I am still holding onto them.
>>
>> Git 2.27-rc2 will be tagged soon, but most of the topics planned for
>> it are already in 'master'.
>>
>> You can find the changes described here in the integration branches
>> of the repositories listed at
>>
>>     http://git-blame.blogspot.com/p/git-public-repositories.html
>
> Looks like the scissors docfix at
> https://lore.kernel.org/git/20200522142611.1217757-1-newren@gmail.com/
> may have fallen through the cracks.  It's not important for 2.27, but
> could that be picked up at least for pu?

Indeed, as I do not necessarily scan through messages all the way to the end, when it is clear that patches are discussed and polished by capable hands. I'd simply wait for the next round before jumping in in such a case, and shift the focus to other topics and/or tasks.

I haven't read the documentation patch yet, and I do not see anybody else reading it, either, so it probably is outside the scope for the upcoming release.

Thanks for pinging.