Mercurial > hg
comparison mercurial/help/phases.txt @ 20299:b4b77909318f
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.
| author | Pierre-Yves David <pierre-yves.david@ens-lyon.org> |
|---|---|
| date | Sun, 17 Nov 2013 11:30:17 -0500 |
| parents | 9ef92384415c |
| children | f1a3ae7c15df |
comparison
equal
deleted
inserted
replaced
| 20298:9d350fa0708e | 20299:b4b77909318f |
|---|---|
| 56 | 56 |
| 57 .. note:: | 57 .. note:: |
| 58 Servers running older versions of Mercurial are treated as | 58 Servers running older versions of Mercurial are treated as |
| 59 publishing. | 59 publishing. |
| 60 | 60 |
| 61 .. note:: | |
| 62 Changesets in secret phase are not exchanged with the server. This | |
| 63 applies to their content: file names, file contents, and changeset | |
| 64 metadata. For technical reasons, the identifier (e.g. d825e4025e39) | |
| 65 of the secret changeset may be communicated to the server. | |
| 66 | |
| 67 | |
| 61 Examples | 68 Examples |
| 62 ======== | 69 ======== |
| 63 | 70 |
| 64 - list changesets in draft or secret phase:: | 71 - list changesets in draft or secret phase:: |
| 65 | 72 |