commit: explicitly document the existence of "last-message.txt" stable
authorGreg Ward <greg-hg@gerg.ca>
Sat, 14 Aug 2010 14:57:33 +0200
branchstable
changeset 11877 8f40125a0ed8
parent 11845 85de44ae0238
child 11881 2da0cf99b642
commit: explicitly document the existence of "last-message.txt"
mercurial/commands.py
--- a/mercurial/commands.py	Sat Aug 14 01:31:57 2010 +0200
+++ b/mercurial/commands.py	Sat Aug 14 14:57:33 2010 +0200
@@ -739,8 +739,10 @@
     If you are committing the result of a merge, do not provide any
     filenames or -I/-X filters.
 
-    If no commit message is specified, the configured editor is
-    started to prompt you for a message.
+    If no commit message is specified, Mercurial starts your
+    configured editor where you can enter a message. In case your
+    commit fails, you will find a backup of your message in
+    ``.hg/last-message.txt``.
 
     See :hg:`help dates` for a list of formats valid for -d/--date.