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

Re: What's cooking in git.git (Mar 2026, #08)

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 22, 2026, 17:53 UTC
Message-ID
<xmqqpl4v92eb.fsf@gitster.g>
In-Reply-To
<20260322141517.54890-1-shreyanshpaliwalcmsmn@gmail.com>
Shreyansh Paliwal <shreyanshpaliwalcmsmn@gmail.com> writes:
> Though you fixed the conflicts while merging the old version, commit is not
> yet replaced <20260318090546.1213077-1-shreyanshpaliwalcmsmn@gmail.com>.

The end result would be better with the initial one after all, as it could be merged down without somebody else's patch you do not need to depend on, so let's keep it as-is. I'll need to replace the status comment, as this has been reviewed and looks good, and it also seems nobody complains about what the patch does.

Thanks.
Previous: Shreyansh PaliwalNext: René Scharfe
Message 3 of 8 in “What's cooking in git.git (Mar 2026, #08)”
  1. Junio C HamanoMar 22, 2026
  2. Shreyansh PaliwalMar 22, 2026
  3. Junio C HamanoMar 22, 2026
  4. René ScharfeMar 22, 2026
  5. Junio C HamanoMar 22, 2026
  6. Johannes SchindelinMar 23, 2026
  7. Junio C HamanoMar 23, 2026
  8. Jeff KingMar 22, 2026

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.