From: Elijah Newren <newren@gmail.com>
Date: Thu, 20 Nov 2025 07:02:20 GMT
Subject: Re: [PATCH v6 04/11] builtin: add new "history" command
Message-ID: <CABPp-BGSYKPB7met4U_4ECNgA9vb5y_AWnMWfpiisOHnd_OyhQ@mail.gmail.com>
In-Reply-To: <20251027-b4-pks-history-builtin-v6-4-407dd3f57ad3@pks.im>

In addition to what Phillip commented on...

On Mon, Oct 27, 2025 at 4:34 AM Patrick Steinhardt <ps@pks.im> wrote:
>
> When rewriting history via git-rebase(1) there are a couple of very
> common use cases:
>
>   - The ordering of two commits should be reversed.
>
>   - A commit should be split up into two commits.
>
>   - A commit should be dropped from the history completely.
>
>   - Multiple commits should be squashed into one.
>
> While these operations are all doable, it often feels needlessly kludgey
> to do so by doing an interactive rebase, using the editor to say what
> one wants, and then perform the actions. Furthermore, some operations
> like splitting up a commit into two are way more involved than that and
> require a whole series of commands.
>
> Add a new "history" command to plug this gap. This command will have
> several different subcommands to imperatively rewrite history for common
> use cases like the above. These subcommands will be implemented in
> subsequent commits.

"...*Some of* these subcommands will be implemented...", right?  You
only implement two of them in this series, not all of them, or am I
reading wrong?