docs: document how to strip changesets from a review repository; r?mcote draft
authorGregory Szorc <gps@mozilla.com>
Wed, 26 Apr 2017 11:46:12 -0700
changeset 10869 027ee34900eb02ba7e5731ba9919ec68468db718
parent 10868 08a627572c1df33ba3785e2b74f68730d9667c3e
push id1641
push userbmo:gps@mozilla.com
push dateWed, 26 Apr 2017 18:46:15 +0000
reviewersmcote
docs: document how to strip changesets from a review repository; r?mcote MozReview-Commit-ID: 9rLbw9zFOac
docs/hgmo/ops.rst
--- a/docs/hgmo/ops.rst
+++ b/docs/hgmo/ops.rst
@@ -135,16 +135,31 @@ Then, simply enter requested data in the
 should be created.
 
 .. note::
 
    This requires root SSH access to reviewboard-hg1.dmz.scl.mozilla.com
    and for the specified Bugzilla account to have admin privileges on
    reviewboard.mozilla.org.
 
+Stripping Changesets from a Review Repository
+=============================================
+
+It is sometimes necessary to remove traces of a changeset from a **review**
+repository. This can be accomplished by running a command from a shell on
+a reviewboard-hg server::
+
+   $ cd /repo/hg/mozilla/<repo>
+   $ sudo -u hg /var/hg/venv_pash/bin/hg --config extensions.strip= strip -r <revision>
+
+.. important::
+
+   If the ``hg`` from the ``pash`` virtualenv isn't used, the pushlog may get
+   corrupted when running ``hg strip``.
+
 Marking Repositories as Read-only
 =================================
 
 Repositories can be marked as read-only. When a repository is read-only,
 pushes are denied with a message saying the repository is read-only.
 
 To mark an individual repository as read-only, create a
 ``.hg/readonlyreason`` file. If the file has content, it will be printed