facebook/sapling
1
1
Fork 0
mirror of https://github.com/facebook/sapling.git synced 2024-10-07 15:27:13 +03:00
Code Issues Projects Releases Wiki Activity

transplant: explain that changesets are copied, not moved

Browse Source
This commit is contained in:
Martin Geisler 2011-03-13 12:43:52 +01:00
parent 43eea49bf4
commit 459f5e46b7
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
hgext/transplant.py
View File

@ -452,8 +452,13 @@ def transplant(ui, repo, *revs, **opts):
'''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)