Re: [PATCH v10 8/8] builtin/history: implement "reword" subcommand
- From
Elijah Newren <newren@gmail.com>
- Date
- Jan 13, 2026, 06:01 UTC
- Message-ID
- <CABPp-BHq35ySWhud-_53BXE1ed=V7MqjrpWDzgWkcs7o_Lum-A@mail.gmail.com>
- In-Reply-To
- <20260112-b4-pks-history-builtin-v10-8-e3c6aa5b4cec@pks.im>
On Mon, Jan 12, 2026 at 6:17 AM Patrick Steinhardt <ps@pks.im> wrote:
Show 24 quoted lines
> > Implement a new "reword" subcommand for git-history(1). This subcommand > is similar to the user performing an interactive rebase with a single > commit changed to use the "reword" instruction. > > The "reword" subcommand is built on top of the replay subsystem > instead of the sequencer. This leads to some major differences compared > to git-rebase(1): > > - We do not check out the commit that is to be reworded and instead > perform the operation in-memory. This has the obvious benefit of > being significantly faster compared to git-rebase(1), but even more > importantly it allows the user to rewrite history even if there are > local changes in the working tree or in the index. > > - We do not execute any hooks, even though we leave some room for > changing this in the future. > > - By default, all local branches that contain the commit will be > rewritten. This especially helps with workflows that use stacked > branches. > > Helped-by: Elijah Newren <newren@gmail.com> > Signed-off-by: Patrick Steinhardt <ps@pks.im>
This patch is now a mixture of my patch and yours; all the changes since your v9 & my patch look good to me.