[PATCH 1 of 7 V1.1 (do not wait for the six other one)] phases: add aformal note that hash of secret changeset may leak outt

Sean Farley sean.michael.farley at gmail.com
Fri Dec 20 14:20:12 CST 2013


pierre-yves.david at ens-lyon.org writes:

> # 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 496d2181cc89482cabd54c52d3ec1f20a2c89177
> # 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,17 @@ 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 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.

The English looks alright to me.


More information about the Mercurial-devel mailing list