transplant: explain that changesets are copied, not moved stable
authorMartin Geisler <mg@lazybytes.net>
Sun, 13 Mar 2011 12:43:52 +0100
branchstable
changeset 13605 888ec2650c2d
parent 13600 bcc59cb3714d
child 13606 1532ed1e50ca
transplant: explain that changesets are copied, not moved
hgext/transplant.py
--- a/hgext/transplant.py	Sat Mar 12 16:00:54 2011 +0100
+++ b/hgext/transplant.py	Sun Mar 13 12:43:52 2011 +0100
@@ -452,8 +452,13 @@
     '''transplant changesets from another branch
 
     Selected changesets will be applied on top of the current working
-    directory with the log of the original changeset. If --log is
-    specified, log messages will have a comment appended of the form::
+    directory with the log of the original changeset. The changesets
+    are copied and will thus appear twice in the history. Use the
+    rebase extension instead if you want to move a whole branch of
+    unpublished changesets.
+
+    If --log is specified, log messages will have a comment appended
+    of the form::
 
       (transplanted from CHANGESETHASH)