Re: [PATCH 0/8] history: introduce "split" subcommand

>
> Hi,
>
> this patch series introduces `git history split` as an easy way to split
> up one commit into multiple commits.

> This subcommand has already been
> introduced in earlier versions of my git-history(1) patch series, but I
> eventually decided to evict them from this series so that we can rather
> focus more on basic decisions.
>
> In any case, the current version of this patch series matches (to the
> best of my knowledge) the latest agreements on the mailing list around
> its behaviour. Most importantly:
>
>   - It will ask for commit messages for both commits, not only the first
>     commit, which has been a bit of a discussion point.
>
>   - It is not possible to edit hunks. This results in a mode where
>     conflicts are not possible as the tree of the second commit will
>     always match the tree of the original commit. Conflict handling for
>     subsequent subcommands will be a bigger topic, as it probably
>     depends on support for first-class conflicts.
>
>   - We also update dependent branches, same as with the latest iteration
>     of `git history reword`.