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

Re: What's cooking in git.git (Jan 2026, #03)

From
KHKristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date
Jan 8, 2026, 13:08 UTC
Message-ID
<44cd16d2-eabf-4ff4-9bc6-da370bbe858d@app.fastmail.com>
In-Reply-To
<xmqq1pk0gvxc.fsf@gitster.g>
Show 11 quoted lines
> * kh/replay-invalid-onto-advance (2026-01-05) 6 commits
>   (merged to 'next' on 2026-01-08 at 1024748f91)
>  + t3650: add more regression tests for failure conditions
>  + replay: die if we cannot parse object
>  + replay: improve code comment and die message
>  + replay: die descriptively when invalid commit-ish is given
>  + replay: find *onto only after testing for ref name
>  + replay: remove dead code and rearrange
>  (this branch is used by ps/history and pw/replay-drop-empty.)
>
>  Test coverage of "git replay" has been improved.
I still disagree with this summary. ;)
<460f1f96-4236-4d19-bdfa-6c86bad811c5@app.fastmail.com>
Show 5 quoted lines
>
>  Will merge to 'master'.
>  cf. <CABPp-BGFNyKkpcWWksqvNqyXspMqfywbYyyhuSUaL41YHNHoNg@mail.gmail.com>
>  source: <V3_CV_replay_die_descr.1a4@msgid.xyz>
>[snip]
Previous: Junio C HamanoNext: Junio C Hamano
Message 2 of 3 in “What's cooking in git.git (Jan 2026, #03)”
  1. Junio C HamanoJan 8, 2026
  2. Kristoffer HaugsbakkJan 8, 2026
  3. Junio C HamanoJan 9, 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.