Re: What's cooking in git.git (May 2025, #06; Tue, 20)

From: Karthik Nayak <karthik.188@gmail.com>
Date: May 22, 2025, 08:57 UTC
Message-ID: <CAOLa=ZQvow9wkxKPFtfLHFxXvBvnZ-U6+qgfVxWoLfuH190Qjg@mail.gmail.com>
In-Reply-To: <xmqqtt5ec8t2.fsf@gitster.g>

Junio C Hamano <gitster@pobox.com> writes:

Show 12 quoted lines

> Karthik Nayak <karthik.188@gmail.com> writes:
>
>>>  Will merge to 'next'?
>>>  source: <20250519-501-update-git-fetch-1-to-use-partial-transactions-v3-0-6cdfd4f769b9@gmail.com>
>>
>> Incase you missed the cover letter: I would say that while this can be
>> merged to 'next', we should delay the merge to 'master' for after the
>> 2.50 release since it can be disruptive. Mostly letting it bake for a
>> longer time before hitting a major release.
>
> What are the things you are so unsure about and guinea pigs who use
> 'next' as their daily driver should watch out for?

The patch series changes two critical sections of the code base and could contain bugs which would disrupt regular workflows. There's no particular part I'm unsure about. But being cautious since the release cycle is coming to the end. So this won't bake in master for long before it gets released.

That said, the series primarily touches The pull and push flow, so any edge cases is something to look out for. Specifically around the usage of hooks with reference updates ('update' and 'reference-transaction').

Thanks