# HG changeset patch
# User Martin Geisler <mg@daimi.au.dk>
# Date 1238862661 -7200
# Node ID cab4a521a3fd60b67b754f68d9fe80bcb9a31075
# Parent  20df260ae30184ed8819c6153e5da978727db4f4
commands: explain when to use resolve -m

diff -r 20df260ae301 -r cab4a521a3fd mercurial/commands.py
--- a/mercurial/commands.py	Sat Apr 04 18:03:03 2009 +0200
+++ b/mercurial/commands.py	Sat Apr 04 18:31:01 2009 +0200
@@ -2343,8 +2343,13 @@
     revisions preserved from the last update or merge. To attempt to
     resolve all unresolved files, use the -a switch.
 
+    If a conflict is resolved manually, please note that the changes
+    will be overwritten if the merge is retried with resolve. The -m
+    switch should be used to mark the file as resolved.
+
     This command will also allow listing resolved files and manually
-    marking and unmarking files as resolved.
+    marking and unmarking files as resolved. All files must be marked
+    as resolved before the new commits are permitted.
 
     The codes used to show the status of files are:
     U = unresolved