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

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

From
Junio C Hamano <gitster@pobox.com>
Date
May 21, 2025, 14:55 UTC
Message-ID
<xmqqtt5ec8t2.fsf@gitster.g>
In-Reply-To
<CAOLa=ZR-OaLPueyRcXYrN0rKPnVXPPmJ6drsmM4eRs-6yKEgQQ@mail.gmail.com>
Karthik Nayak <karthik.188@gmail.com> writes:
Show 7 quoted lines
>>  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?

Previous: Karthik NayakNext: Karthik Nayak
Message 3 of 4 in “What's cooking in git.git (May 2025, #06; Tue, 20)”
  1. Junio C HamanoMay 21, 2025
  2. Karthik NayakMay 21, 2025
  3. Junio C HamanoMay 21, 2025
  4. Karthik NayakMay 22, 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.