bundle operation that matches a given criteria.
The extension sets up a pretxnchangegroup hook, which is executed on every
-push, pull and bundle operation. The hook tries to match every new changeset
+push, pull and bundle operation. The hook tries to match every new changeset
in the changegroup that is being pushed, pulled or bundled into a repository
against a list of "banned" revision sets.
The .hgban file does not need to be committed, although in practice
it usually makes sense to do so.
-2. Set a hgban.revsets key
to one of your mecurial configuration files
+2. Set a hgban.revsets key one of your mecurial configuration files
(i.e. add a "hgban" section, and in it set a "revsets" key).
In order to ban more than one revset using this method you must create a
multi-line configuration key as explained in
This is useful when you want to ban a certain revset but you do not want
to track the fact that you ban that revset in your repository history.
-Note that the extension will match new revisions against any revsets specified
-in the .hgban file or on the hgban.revsets key (i.e. using one method does not
-exclude using the other).
+(Note either or both methods can be used to ban changesets.)
# Ban changeset that adds nuclear launch keys
-# Do not allow John Doe to push any of i
+# Do not allow John Doe to push any of is changes
Alternativelly, instead of using the .hgban file you could set