Re: [RFC] introducing git replay

From: Edmundo Carmona Antoranz <eantoranz@gmail.com>
Date: Apr 13, 2022, 17:49 UTC
Message-ID: <CAOc6etbheKZ9CYJ+6Chz9gDj1WGK_5hQeHYTmhOKiUtDd0RKtQ@mail.gmail.com>
In-Reply-To: <8735iglvxq.fsf@vps.thesusis.net>

On Wed, Apr 13, 2022 at 7:45 PM Phillip Susi <phill@thesusis.net> wrote:

Show 10 quoted lines

>
>
> Edmundo Carmona Antoranz <eantoranz@gmail.com> writes:
>
> > If HEAD and v2.35.0 share the same tree, it _should_ be possible
> > to recreate the commits that make up the range v2.35.0..v2.36.0-rc1
> > on top of HEAD without requiring any real "rebasing". Just creating
>
> Isn't that literally the definition of rebase?
>

Well, yeah. :-) What I mean is to skip the rebase _engine_. No merging/cherry-picking/conflicts along the way of recreating the new revisions. Say, clone the exact same revisions that we want to _rebase_ and adjust their parents, nothing else (or little else, like adjusting the committer).