comparison hgext/transplant.py @ 13605:888ec2650c2d stable

transplant: explain that changesets are copied, not moved
author Martin Geisler <mg@lazybytes.net>
date Sun, 13 Mar 2011 12:43:52 +0100
parents 3da456d0c885
children 1532ed1e50ca
comparison
equal deleted inserted replaced
13600:bcc59cb3714d 13605:888ec2650c2d
450 450
451 def transplant(ui, repo, *revs, **opts): 451 def transplant(ui, repo, *revs, **opts):
452 '''transplant changesets from another branch 452 '''transplant changesets from another branch
453 453
454 Selected changesets will be applied on top of the current working 454 Selected changesets will be applied on top of the current working
455 directory with the log of the original changeset. If --log is 455 directory with the log of the original changeset. The changesets
456 specified, log messages will have a comment appended of the form:: 456 are copied and will thus appear twice in the history. Use the
457 rebase extension instead if you want to move a whole branch of
458 unpublished changesets.
459
460 If --log is specified, log messages will have a comment appended
461 of the form::
457 462
458 (transplanted from CHANGESETHASH) 463 (transplanted from CHANGESETHASH)
459 464
460 You can rewrite the changelog message with the --filter option. 465 You can rewrite the changelog message with the --filter option.
461 Its argument will be invoked with the current changelog message as 466 Its argument will be invoked with the current changelog message as