hg commit doesn't catch changes made during editing of commit messages

Bryan O'Sullivan bos at serpentine.com
Thu Sep 22 23:45:55 CDT 2005

On Thu, 2005-09-22 at 11:45 -0700, Rob Browning wrote:

> If nothing else, would it be possible to just detect that files were
> changed during the commit and just abort/rollback with an error
> message instead of finishing?

The trouble is, that's an obnoxious behaviour, too.  What happens if
you've just typed in a detailed commit message into your editor and the
commit gets rolled back?  Poof!  No more commit message.

I'm not trying to defend the status quo, but I don't want to move the
badness around, either :-)

> Right now, if hg commit doesn't find the logfile specified by "-l", it
> will just continue anyway and launch $EDITOR.

This is now fixed: http://hg.serpentine.com/mercurial/bos

> It would also be nice if there were some way to abort a commit (for
> example, if you realize you've made some kind of mistake while editing
> the commit message).

There is; just exit from the editor without modifying the commit text.


More information about the Mercurial mailing list