git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 25, 2025, 15:03 UTC
Message-ID
<xmqqecv7zwv9.fsf@gitster.g>
In-Reply-To
<CAOLa=ZTXQewoVKLk6DfO79Q9R5keDOeEOWOt9Ejp4O_RQ0Jq8Q@mail.gmail.com>
Karthik Nayak <karthik.188@gmail.com> writes:
Show 30 quoted lines
> 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!
Previous: Karthik NayakNext: Phillip Wood
Message 4 of 7 in “What's cooking in git.git (Jun 2025, #08; Mon, 23)”
  1. Junio C HamanoJun 24, 2025
  2. Junio C HamanoJun 24, 2025
  3. Karthik NayakJun 24, 2025
  4. Junio C HamanoJun 25, 2025
  5. Phillip WoodJun 25, 2025
  6. Junio C HamanoJun 25, 2025
  7. brian m. carlsonJun 25, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.