Re: b4 feature request: run command before rewriting history

["Toke Høiland-Jørgensen" <toke@redhat.com>]

Toke Høiland-Jørgensen <toke@redhat.com> writes:

> Hi Konstantin
>
> I recently started switching my workflow over to 'b4 prep' for preparing
> patches, and am loving the workflow. Thanks a lot for working on this!
>
> However, I ran into one little snag, that I'm hoping could be fixed with
> a new b4 feature: I am also a big fan of 'stacked git' (stgit)[0], and
> often use that instead of 'rebase -i' when preparing a series for
> submission.
>
> So naturally, I want to combine 'b4 prep' with stgit. The problem here
> is that stgit maintains its own state for the branches it manages, and
> gets awfully confused if the git history is rewritten underneath it.
> It's still possible to use it with 'b4 prep', as long as I remember to
> do 'stg commit --all' before running any of the b4 commands. And, well,
> guess what I already forgot several times? :)
>
> So, my feature request is this: add support to b4 for a hook command
> that is executed before any operation that will rewrite history - and
> abort the rewriting if the command fails. That way, I can make sure that
> I don't forget to clear the stgit state before running b4, saving me
> from the pain of dealing with a confused tool.
>
> Do you think this would be feasible to implement?

Hi Konstantin

Friendly ping on the above? :)

-Toke