[issue2259] backout should not commit without question if commit message file was not changed

[Jørgen Austvik <bugs@mercurial.selenic.com> at mercurial.selenic.com]

New submission from Jørgen Austvik <jaustvik at acm.org>:

What I did:

$ hg backout tip

I got a vi editor with a commit message, figured that if I went
through the trouble to not get a commit message for the merge, this
was the wrong command, so i ":q!" (no write).

Output from hg:

Output:
removing example_file
changeset 1033:e9a5491a4636 backs out changeset 1032:976a92922ca5

I wish hg to not take any action if I decide not to write the file (even
though I did not :cq!).

I think the alternative from SVN is more user friendly:

$ svn ci # vim prompted, ":q!" on empty message
Log message unchanged or not specified
(a)bort, (c)ontinue, (e)dit:
a

Please check if the message is unchanged in hg, and if so ask the user for a
confirmation.

----------
messages: 12931
nosy: austvik
priority: wish
status: unread
title: backout should not commit without question if commit message file was not changed

____________________________________________________
Mercurial issue tracker <bugs at mercurial.selenic.com>
<http://mercurial.selenic.com/bts/issue2259>
____________________________________________________