Re: What's cooking in git.git (Jun 2025, #08; Mon, 23)

[Junio C Hamano <gitster@pobox.com>]

Karthik Nayak <karthik.188@gmail.com> writes:

> Junio C Hamano <gitster@pobox.com> writes:
>
>> * kn/fetch-push-bulk-ref-update (2025-05-19) 4 commits
>>  - receive-pack: use batched reference updates
>>  - send-pack: fix memory leak around duplicate refs
>>  - fetch: use batched reference updates
>>  - refs: add function to translate errors to strings
>>  (this branch is used by kn/fetch-push-bulk-ref-update-fixup.)
>>
>>  "git push" and "git fetch" are taught to update refs in batches to
>>  gain performance.
>>
>>  Tentatively kicked out of 'next' to give its fix-up topic a chance to reboot.
>>  source: <20250519-501-update-git-fetch-1-to-use-partial-transactions-v3-0-6cdfd4f769b9@gmail.com>
>>
>>
>> * kn/fetch-push-bulk-ref-update-fixup (2025-06-20) 3 commits
>>  - receive-pack: handle reference deletions separately
>>  - refs/files: skip updates with errors in batched updates
>>  - Merge branch 'kn/fetch-push-bulk-ref-update' into kn/fetch-push-bulk-ref-update-fixup
>>  (this branch uses kn/fetch-push-bulk-ref-update.)
>>
>>  Additional fixes to the base topic.
>>
>>  Comments?
>>  source: <20250620-6769-address-test-failures-in-the-next-branch-caused-by-batched-reference-updates-v5-0-f35ee6b59a82@gmail.com>
>>
>
> This was reviewed by Christian and you. The latest version addresses all
> the comments, do we need some more eyes here?

OK, then.  Let's move the commits from the latter on top of the former
and mark the former for 'next'.

Thanks!