Ramkumar Ramachandra <artag...@gmail.com> writes:
> On the latest git, I noticed that a rebase --onto doesn't abort
> properly. Steps to reproduce:
> # on some topic branch
> $ git rebase --onto master @~10
> ^C # quickly!
> $ git rebase --abort
> # HEAD is still detached
I do not think --abort was designed to abort an uncontrolled stop
like ^C in the first place. To allow that kind of "recovery", you
need to teach "rebase" to first record the state you would want to
go back to before doing anything, but then what happens if the ^C
comes when you are still in the middle of doing so?
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html