Re: [PATCH] rebase: mention --abort alongside --continue

[Junio C Hamano <gitster@pobox.com>]

Phillip Wood <phillip.wood123@gmail.com> writes:

> To me aborting a rebase because an exec command failed is almost never a 
> sensible route forward and we should not be encouraging users to abort 
> after a failed test - surely the sensible thing to do in that case is 
> fix the problem with "git commit --amend" and continue the rebase.

My conclusion, from my own experience with "git rebase", is the
same.

I wonder if the workflow that benefits from this "if exec fails,
give up and forget the whole thing" behavior is actually quite
different from what we consider the "normal" use of the command?
Perhaps the user is not interested in "rebasing" the history at
all, but is instead running a check on each and every commit.
That is, a more expensive version of:

        for commit in $(git rev-list bottom..top)
        do
                git reset --hard "$commit" &&
                do the exec command || break
        done

that just happens to be shorter to type?