[PATCH 1 of 4] commit: try to clarify when to use --new-branch
timeless
timeless at mozdev.org
Mon Dec 7 20:23:47 UTC 2015
# HG changeset patch
# User timeless <timeless at mozdev.org>
# Date 1448909767 0
# Mon Nov 30 18:56:07 2015 +0000
# Node ID 4eb33ce681a1ac1df40845145e336c5c39b7497a
# Parent 30a20167ae29e1874163b59a489de0cb1d859565
commit: try to clarify when to use --new-branch
diff --git a/mercurial/commands.py b/mercurial/commands.py
--- a/mercurial/commands.py
+++ b/mercurial/commands.py
@@ -1568,6 +1568,13 @@
head closed. When all heads of a branch are closed, the branch
will be considered closed and no longer listed.
+ .. note::
+
+ If you are thinking about closing a branch, but you never shared
+ it, you should consider making it secret (see :hg:`help phase`) or
+ obsolete (see :hg:`help obsolete`), or stripping it
+ (see :hg:`help strip`) instead of merely closing it.
+
The --amend flag can be used to amend the parent of the
working directory with a new commit that contains the changes
in the parent in addition to those currently reported by :hg:`status`,
More information about the Mercurial-devel
mailing list