Re: [PATCH v8 7/7] builtin/history: implement "reword" subcommand

From: D. Ben Knoble <ben.knoble@gmail.com>
Date: Jan 7, 2026, 18:01 UTC
Message-ID: <CALnO6CDG222mhCeWyBCpGU3fQiHPVwBh=5EygRFrFN3JOcx6Sw@mail.gmail.com>
In-Reply-To: <20260107-b4-pks-history-builtin-v8-7-18e9779e3a26@pks.im>

On Wed, Jan 7, 2026 at 5:10 AM Patrick Steinhardt <ps@pks.im> wrote:

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

Show 16 quoted lines

> diff --git a/Documentation/git-history.adoc b/Documentation/git-history.adoc
> index 5a9d931efc..4eea317e5c 100644
> --- a/Documentation/git-history.adoc
> +++ b/Documentation/git-history.adoc
> @@ -32,8 +32,9 @@ Overall, linkgit:git-history[1] aims to provide a more opinionated way to modify
>  your commit history that is simpler to use compared to linkgit:git-rebase[1] in
>  general.
>
> -If you want to reapply a range of commits onto a different base, or interactive
> -rebases if you want to edit a range of commits.
> +Use linkgit:git-rebase[1] if you want to reapply a range of commits onto a
> +different base, or interactive rebases if you want to edit a range of commits
> +at once.
>
>  LIMITATIONS
>  -----------

Ah, looks like this commit fixed one of my befuddlements during the range-diff. Bad history edit? :)