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.
This commit is contained in:
Pierre-Yves David 2013-11-17 11:30:17 -05:00
parent 5c02304224
commit 0420ab83f5

View File

@ -58,6 +58,13 @@ See :hg:`help config` for more information on configuration files.
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
========