All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Toon Claes <toon@iotcl.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2] replay: support replaying down from root commit
Date: Tue, 24 Mar 2026 12:53:03 -0700	[thread overview]
Message-ID: <xmqqtsu5xaw0.fsf@gitster.g> (raw)
In-Reply-To: <20260324-toon-replay-down-to-root-v2-1-34e723489f6e@iotcl.com> (Toon Claes's message of "Tue, 24 Mar 2026 20:35:41 +0100")

Toon Claes <toon@iotcl.com> writes:

> git-replay(1) doesn't allow replaying commits all the way down to the
> root commit. Fix that.
>
> Signed-off-by: Toon Claes <toon@iotcl.com>
> ---
> These changes might conflict Siddharth's series[1] to add '--revert' to
> git-replay(1), although resolving that should be trivial.

True.  This round looks great to me.  Will queue.

Shall we mark the topic for 'next' now?

Thanks.

  reply	other threads:[~2026-03-24 19:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17 18:56 [PATCH] replay: support replaying down from root commit Toon Claes
2026-03-17 19:59 ` Junio C Hamano
2026-03-24 17:25   ` Toon Claes
2026-03-24 19:35 ` [PATCH v2] " Toon Claes
2026-03-24 19:53   ` Junio C Hamano [this message]
2026-03-25 10:00     ` Christian Couder
2026-03-25 12:19       ` Ben Knoble
2026-03-25 15:35         ` Make git-replay(1) warn if revision-range isn't a range (was: Re: [PATCH v2] replay: support replaying down from root commit) Toon Claes
2026-03-25 15:32       ` [PATCH v2] replay: support replaying down from root commit Toon Claes
2026-03-25 15:37         ` Toon Claes
2026-03-27 16:45         ` Junio C Hamano
2026-03-31 10:34           ` Christian Couder
2026-03-31 16:20             ` Junio C Hamano
2026-04-02  9:08               ` Toon Claes
2026-04-02 17:02                 ` Junio C Hamano
2026-04-03  6:49                   ` Christian Couder
2026-03-25 16:49       ` Junio C Hamano

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=xmqqtsu5xaw0.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.