Re: What's cooking in git.git (Mar 2026, #11)
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Mar 27, 2026, 16:13 UTC
- Message-ID
- <xmqq1ph5mesp.fsf@gitster.g>
- In-Reply-To
- <CAP8UFD3kxL5xAcd2OBNmLFMdBaRLgB0WKtvSkuO2m7GP=kZK6Q@mail.gmail.com>
Christian Couder <christian.couder@gmail.com> writes:
Show 13 quoted lines
> On Fri, Mar 27, 2026 at 12:17 AM Junio C Hamano <gitster@pobox.com> wrote: > >> * tc/replay-down-to-root (2026-03-24) 1 commit >> - replay: support replaying down from root commit >> >> git replay now supports replaying down to the root commit. >> >> Will merge to 'next'? >> source: <20260324-toon-replay-down-to-root-v2-1-34e723489f6e@iotcl.com> > > As Toon said that the silent failure in case of "topic" instead of > "main..topic" will be addressed in a separate series, I am fine with > merging as is.
I'll have to go back to list to find the original discussion to refresh my memory to know what "main..topic" vs "topic" is about, though X-<.
Show 14 quoted lines
>> * sa/replay-revert (2026-03-25) 2 commits >> - replay: add --revert mode to reverse commit changes >> - sequencer: extract revert message formatting into shared function >> (this branch is used by tc/replay-ref.) >> >> "git replay" (experimental) learns, in addition to "pick" and >> "replay", a new operating mode "revert". >> >> Will merge to 'next'? >> source: <20260325202354.10628-1-siddharthasthana31@gmail.com> > > It looks good to me, and I think the v6 properly addresses the latest > few small issues that were found. Previously Phillip also seemed OK > with merging except for the issues that are now fixed.
Thanks.