Duy Nguyen <pclouds@xxxxxxxxx> writes: > rebase and cherry-pick/revert are not exactly in the same situation. > When cherry-pick/revert in "continue/abort" mode, there's usually some > conflicted files and it's easy to notice. > > But an interactive rebase could stop at some commit with clean > worktree (the 'edit' command). Then I could even add some more commits > on top. I don't see how 'rebase --abort' can know my intention in this > case, whether I tried (with some new commits) and failed, and want to > revert/abort the whole thing, moving HEAD back to the original; or > whether I forgot I was in the middle of rebase and started to do > something else, and --abort needs to keep HEAD where it is. OK.