Mercurial > public > mercurial-scm > hg-stable

comparison mercurial/commands.py @ 19935:4f53de036af8

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
push: add more detailed explanation about "--force" to online help document This patch adds more detailed explanation about "--force" to online help document of "hg push" to prevent novice users to execute "push --force" easily without understanding about problems of multiple branch heads in the repository.
author FUJIWARA Katsunori <foozy@lares.dti.ne.jp>
date Thu, 03 Oct 2013 23:16:06 +0900
parents e48c70451afc
children 2bf99bc5077a
comparison
equal deleted inserted replaced
19934:bfc6ed892349 19935:4f53de036af8
4649 4649
4650 Use --new-branch if you want to allow push to create a new named 4650 Use --new-branch if you want to allow push to create a new named
4651 branch that is not present at the destination. This allows you to 4651 branch that is not present at the destination. This allows you to
4652 only create a new branch without forcing other changes. 4652 only create a new branch without forcing other changes.
4653 4653
4654 Use -f/--force to override the default behavior and push all 4654 .. note::
4655 changesets on all branches. 4655 Extra care should be used with the -f/--force option,
4656 which will push all new heads on all branches, an action which will
4657 almost always cause confusion for collaborators.
4656 4658
4657 If -r/--rev is used, the specified revision and all its ancestors 4659 If -r/--rev is used, the specified revision and all its ancestors
4658 will be pushed to the remote repository. 4660 will be pushed to the remote repository.
4659 4661
4660 If -B/--bookmark is used, the specified bookmarked revision, its 4662 If -B/--bookmark is used, the specified bookmarked revision, its