Hi! I'm using git 2.24 (or, a variant of that packaged my distro -- I can try to build my own if this is deemed not reproducible), and I feel like I've been seeing a regression here: Previously, when reverting multiple commits (with the default --edit behavior), as soon as I'm done editing the first revert commit message, the second revert commit pops up an editor, and I'm on my way. Now, it seems to require an extra 'git revert --continue' prompt in between, yet it doesn't actually recommend that. This is highly confusing, and seemingly unnecessary. An annotated transcript provided below. Note that none of this happens with --no-edit; my reverts happen smoothly, with no extra need for --continue. Regards, Brian $ mkdir tmp $ cd tmp /tmp$ git init Initialized empty Git repository in [...]/tmp/.git/ /tmp$ touch foo /tmp$ git add foo /tmp$ echo bar >> foo /tmp$ git commit -am baz [master (root-commit) a388f78d9013] baz 1 file changed, 1 insertion(+) create mode 100644 foo /tmp$ echo pow >> foo /tmp$ git commit -am whizzbang [master 51753222dd9a] whizzbang 1 file changed, 1 insertion(+) /tmp$ echo pop >> foo /tmp$ git commit -am nothing [master 7153607b11e0] nothing 1 file changed, 1 insertion(+) /tmp$ git revert HEAD HEAD^ ## EDITOR pops up, as expected [master 586469974ec2] Revert "nothing" 1 file changed, 1 deletion(-) On branch master Revert currently in progress. nothing to commit, working tree clean ## Unexpected, confusing pause? No prompt to '--continue' /tmp$ git log --oneline 586469974ec2 (HEAD -> master) Revert "nothing" 7153607b11e0 nothing 51753222dd9a whizzbang a388f78d9013 baz /tmp$ git status On branch master Revert currently in progress. (run "git revert --continue" to continue) (use "git revert --skip" to skip this patch) (use "git revert --abort" to cancel the revert operation) nothing to commit, working tree clean /tmp$ git revert --continue ## EDITOR pops up, as expected [master b8dd23f61d07] Revert "whizzbang" 1 file changed, 1 deletion(-) On branch master Revert currently in progress. nothing to commit, working tree clean ## Unexpected state; both reverts happened, but revert is still in progress? /tmp$ git log --oneline b8dd23f61d07 (HEAD -> master) Revert "whizzbang" 586469974ec2 Revert "nothing" 7153607b11e0 nothing 51753222dd9a whizzbang a388f78d9013 baz /tmp$ git status On branch master Revert currently in progress. (run "git revert --continue" to continue) (use "git revert --skip" to skip this patch) (use "git revert --abort" to cancel the revert operation) nothing to commit, working tree clean ## OK...I'll run it one more time. /tmp$ git revert --continue /tmp$ git status On branch master nothing to commit, working tree clean ## *Now* I'm done /tmp$ git log --oneline b8dd23f61d07 (HEAD -> master) Revert "whizzbang" 586469974ec2 Revert "nothing" 7153607b11e0 nothing 51753222dd9a whizzbang a388f78d9013 baz
