phases: add a formal note that hash of secret changeset may leak out
authorPierre-Yves David <pierre-yves.david@ens-lyon.org>
Sun, 17 Nov 2013 11:30:17 -0500
changeset 20299 b4b77909318f
parent 20298 9d350fa0708e
child 20300 0076643077a3
phases: add a formal note that hash of secret changeset may leak out For technical reason (discovery, obsolescence marker) the hash of secret changeset are communicated outside of your repo. We clarifie that in the help so that people does not used hash of secret changeset as nuclear launch code.
mercurial/help/phases.txt
--- a/mercurial/help/phases.txt	Sat Nov 16 15:54:41 2013 -0500
+++ b/mercurial/help/phases.txt	Sun Nov 17 11:30:17 2013 -0500
@@ -58,6 +58,13 @@
   Servers running older versions of Mercurial are treated as
   publishing.
 
+.. note::
+   Changesets in secret phase are not exchanged with the server. This
+   applies to their content: file names, file contents, and changeset
+   metadata. For technical reasons, the identifier (e.g. d825e4025e39)
+   of the secret changeset may be communicated to the server.
+
+
 Examples
 ========