From: Junio C Hamano <gitster@pobox.com>
To: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2026, #03)
Date: Fri, 09 Jan 2026 06:01:09 -0800 [thread overview]
Message-ID: <xmqqpl7ivqai.fsf@gitster.g> (raw)
In-Reply-To: <44cd16d2-eabf-4ff4-9bc6-da370bbe858d@app.fastmail.com> (Kristoffer Haugsbakk's message of "Thu, 08 Jan 2026 14:08:33 +0100")
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:
>> * 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>
Thanks for reminding. Yes, I too disagree with it. I knew the main
change between the original two patches will need to be updated when
I first wrote it to queue the initial version, but it certainly is
not true with the main change (split across 5 patches now).
prev parent reply other threads:[~2026-01-09 14:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 11:56 What's cooking in git.git (Jan 2026, #03) Junio C Hamano
2026-01-08 13:08 ` Kristoffer Haugsbakk
2026-01-09 14:01 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqpl7ivqai.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kristofferhaugsbakk@fastmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox