Mercurial > hg-stable
changeset 24880:5e111acc1170 stable
censor: remove meaningless explanation about .hgcensored
There is no code path handling ".hgcensored" in Mercurial source tree.
This meaningless explanation may make users misunderstand about
censor.
| author | FUJIWARA Katsunori <foozy@lares.dti.ne.jp> |
|---|---|
| date | Thu, 30 Apr 2015 03:39:39 +0900 |
| parents | b3142ea2a0d4 |
| children | 51844b8b5017 |
| files | hgext/censor.py |
| diffstat | 1 files changed, 0 insertions(+), 6 deletions(-) [+] |
line wrap: on
line diff
--- a/hgext/censor.py Wed Apr 29 23:07:34 2015 +0900 +++ b/hgext/censor.py Thu Apr 30 03:39:39 2015 +0900 @@ -17,12 +17,6 @@ * Licensed data/code/libraries for which the license has expired * Personally Identifiable Information or other private data -Censored file revisions are listed in a tracked file called .hgcensored stored -in the repository root. The censor command adds an entry to the .hgcensored file -in the working directory and commits it (much like ``hg tag`` and .hgtags). The -censored file data is then replaced with a pointer to the new commit, enabling -verification. - Censored nodes can interrupt mercurial's typical operation whenever the excised data needs to be materialized. Some commands, like ``hg cat``/``hg revert``, simply fail when asked to produce censored data. Others, like ``hg verify`` and