public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: git@vger.kernel.org,  Toon Claes <toon@iotcl.com>,
	 Phillip Wood <phillip.wood123@gmail.com>
Subject: Re: What's cooking in git.git (Mar 2026, #11)
Date: Fri, 27 Mar 2026 09:13:10 -0700	[thread overview]
Message-ID: <xmqq1ph5mesp.fsf@gitster.g> (raw)
In-Reply-To: <CAP8UFD3kxL5xAcd2OBNmLFMdBaRLgB0WKtvSkuO2m7GP=kZK6Q@mail.gmail.com> (Christian Couder's message of "Fri, 27 Mar 2026 09:07:26 +0100")

Christian Couder <christian.couder@gmail.com> writes:

> 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-<.

>> * 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.

      reply	other threads:[~2026-03-27 16:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26 23:16 What's cooking in git.git (Mar 2026, #11) Junio C Hamano
2026-03-27  7:35 ` Patrick Steinhardt
2026-03-27 16:08   ` Junio C Hamano
2026-03-27  8:07 ` Christian Couder
2026-03-27 16:13   ` 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=xmqq1ph5mesp.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=phillip.wood123@gmail.com \
    --cc=toon@iotcl.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