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

Re: What's cooking in git.git (Dec 2025, #09)

From
KHKristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date
Dec 30, 2025, 14:33 UTC
Message-ID
<460f1f96-4236-4d19-bdfa-6c86bad811c5@app.fastmail.com>
In-Reply-To
<xmqqa4z0f5dq.fsf@gitster.g>
On Tue, Dec 30, 2025, at 14:47, Junio C Hamano wrote:
Show 5 quoted lines
> * kh/replay-invalid-onto-advance (2025-12-22) 2 commits
>  - t3650: add more regression tests for failure conditions
>  - replay: die descriptively when invalid commit-ish
>
>  Test coverage of "git replay" has been improved.

The main change is a better error message when you give a bad argument to `--onto`. The improved test coverage is secondary but related since the coverage for simple die conditions (like bad `--onto` argument) is poor. (Like the mistake that you pointed out;[1] I was about to make the error message for `--advance` slightly worse. But the test for “argument to --advance must be a reference” will make it harder for me to make that mistake in the future.)

The second version is coming now.
🔗 1: https://lore.kernel.org/git/xmqqpl85pb7k.fsf@gitster.g/
>
>  Expecting a rework on the bottom patch.
>  source: <CV_replay_die_descr.13f@msgid.xyz>
Previous: Junio C HamanoNext: K Jayatheerth
Message 2 of 3 in “What's cooking in git.git (Dec 2025, #09)”
  1. Junio C HamanoDec 30, 2025
  2. Kristoffer HaugsbakkDec 30, 2025
  3. K JayatheerthDec 30, 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.