[PATCH 1 of 7] phases: add a formal note that hash of secret changeset may leak out

[pierre-yves.david at ens-lyon.org]

# HG changeset patch
# User Pierre-Yves David <pierre-yves.david at ens-lyon.org>
# Date 1384705817 18000
#      Sun Nov 17 11:30:17 2013 -0500
# Node ID 2f303c30177f75adf0d9f97955504e0938752fa4
# Parent  6c1adf2067bb7c225f96cf253e9e228b5a7cdcf4
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.

diff --git a/mercurial/help/phases.txt b/mercurial/help/phases.txt
--- a/mercurial/help/phases.txt
+++ b/mercurial/help/phases.txt
@@ -56,10 +56,16 @@ See :hg:`help config` for more informati
 
 .. note::
   Servers running older versions of Mercurial are treated as
   publishing.
 
+.. note::
+    Changesets in secret phase are not exchanged the secret. This applies to
+    they content: files name, files content and changeset metadata. For
+    technical reason, the hash of secret changeset may be communicated to the
+    server.
+
 Examples
 ========
 
  - list changesets in draft or secret phase::