# HG changeset patch
# User Pierre-Yves David <pierre-yves.david@octobus.net>
# Date 2023-12-01 21:25:52
# Node ID 51056bedbe0d3fd861e58d62c40dc6869ff05960
# Parent  47a34afda7ad3609a0fe4b803b9bcaf44a413cd5

censor: mention that we check the heads in the help

And add a message to will explain the possibly long time spent doing this.

diff --git a/hgext/censor.py b/hgext/censor.py
--- a/hgext/censor.py
+++ b/hgext/censor.py
@@ -22,7 +22,9 @@ data needs to be materialized. Some comm
 simply fail when asked to produce censored data. Others, like ``hg verify`` and
 ``hg update``, must be capable of tolerating censored data to continue to
 function in a meaningful way. Such commands only tolerate censored file
-revisions if they are allowed by the "censor.policy=ignore" config option.
+As having a censored version in a checkout is impractical. The current head
+revisions of the repository are checked. If the revision to be censored is in
+any of them the command will abort.
 
 A few informative commands such as ``hg grep`` will unconditionally
 ignore censored data and merely report that it was encountered.