mozext: clarify some changes in the docstring (Bug 1569734) r=smacleod
authorConnor Sheehan <>
Wed, 31 Jul 2019 21:08:58 +0000
changeset 7140 0e60a3fd054184576544c4c15227f9c327e7e7b0
parent 7139 e8bf67866f28265ada769fa62edd61faa9a9e19e
child 7141 5e857d4f3091d514c2a104502c816f41d5299dcc
push id3551
push dateWed, 31 Jul 2019 21:22:35 +0000
treeherderversion-control-tools@5e857d4f3091 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
mozext: clarify some changes in the docstring (Bug 1569734) r=smacleod Differential Revision:
--- a/hgext/mozext/
+++ b/hgext/mozext/
@@ -6,78 +6,25 @@
 This extension adds Mozilla-centric commands and functionality to Mercurial
 to enable contributors to Firefox and related applications to be more
 Included are commands that interface with Mozilla's automation infrastructure.
 These allow developers to quickly check the status of repositories and builds
 without having to leave the comfort of the terminal.
-Known Mozilla Repositories
-This extension teaches Mercurial about known Mozilla repositories.
-Each main mozilla-central clone is given a common name. e.g. "mozilla-central"
-becomes "central" and "mozilla-inbound" becomes "inbound." In addition,
-repositories have short aliases to quickly refer to them. e.g.
-"mozilla-central" is can be references by "m-c" or "mc."
-The mechanism to resolve a repository string to a repository instance is
-supplemented with these known aliases. For example, to pull from
-mozilla-central, you can simply run `hg pull central`. There is no need to set
-up the [paths] section in your hgrc!
-To view the list of known repository aliases, run `hg moztrees`.
-Unified Repositories
-Gecko code is developed in parallel across a number of repositories that are
-cloned from the canonical repository, mozilla-central. Seasoned developers
-typically interact with multiple repositories.
-This extension provides mechanisms to create and maintain a single Mercurial
-repository that contains changesets from multiple "upstream" repositories.
-The recommended method to create a unified repository is to run `hg
-cloneunified`. This will pull changesets from all major release branches and
-Once you have a unified repository, you can pull changesets from repositories
-by using `hg pull`, likely by specifying one of the tree aliases (see `hg
-One needs to be careful when pushing changesets when operating a unified
-repository. By default, `hg push` will attempt to push all local changesets not
-in a remote. This is obviously not desired (you wouldn't want to push
-mozilla-central to mozilla-beta)! Instead, you'll want to limit outgoing
-changesets to a specific head or revision. You can specify `hg push -r REV`.
-Remote References
-When pulling from known Gecko repositories, this extension automatically
-creates references to branches on the remote. These can be referenced via
-the revision <tree>/<name>. e.g. 'central/default'.
-Remote refs are read-only and are updated automatically during repository pull
-and push operations.
-This feature is similar to Git remote refs.
 Pushlog Data
 This extension supports downloading pushlog data from Mozilla's repositories.
 Pushlog data records who pushed changesets where and when.
 To use this functionality, you'll need to sync pushlog data from the server to
 the local machine. This facilitates rapid data lookup and can be done by
-running `hg pushlogsync`.
+running `hg pull` from the specified repo with this extension installed.
 Once pushlog data is synced, you can use `hg changesetpushes` to look up push
 information for a specific changeset.
 Bug Info
 Information about bugs is extracted from commit messages as changesets are
@@ -123,21 +70,23 @@ reviewer(REVIEWER)
    the future, we may consult a database of known aliases, etc.
    Retrieve changesets that have a reviewer marked.
    Retrieve changesets that are currently in the specified tree.
-   Trees are specified with a known alias. e.g. ``tree(central)``.
+   Trees are specified with a known alias, typically a tree from the `firefoxtrees`
+   extension, e.g. ``tree(central)``
    It's possible to see which changesets are in some tree but not others.
    e.g. to find changesets in *inbound* that haven't merged to *central*
-   yet, do ``tree(inbound) - tree(central)``.
+   yet, do ``tree(inbound) - tree(central)``. This is essentially the same
+   as ``::inbound - ::central``.
 This extension provides keywords that can used with templates.
    The bug primarily associated with a changeset.
@@ -148,40 +97,23 @@ bugs
    The version number of the first release channel release a changeset
    was present in.
    The version number of the first beta channel release a changeset was
    present in.
-   The version number of the first aurora channel release a changeset was
-   present in.
    The version number of the first nightly channel release a changeset was
    present in.
-   The date of the first Aurora a changeset was likely present in.
-   This value may not be accurate. The value is currently obtained by
-   querying the pushlog data to see when a changeset was pushed to this
-   channel. The date of the next Aurora is then calculated from that
-   (essentially looking for the next early morning Pacific time day).
-   Aurora releases are not always consistent. A more robust method of
-   calculation involves grabbing information from release engineering
-   servers.
    The date of the first Nightly a changeset was likely present in.
-   See auroradate for accuracy information.
    The username of the first person who pushed this changeset.
    The name of the first tree this changeset was pushed to.
    The URL of the Treeherder results for the first push of this changeset.
@@ -217,18 +149,19 @@ Config Options
 This extension consults the following config options.
    Indicates that this extension is running in *headless* mode. *headless*
    mode is intended for server operation, not local development.
-   Your Mozilla IRC nickname. This string value will be used to look for
-   your reviews and patches.
+   Your Mozilla IRC nickname/Phabricator account name. This string value
+   will be used to look for your reviews and patches, on top of the value
+   set in ``ui.username``.
    When this boolean flag is true, the local SQLite database indexing
    useful lookups (such as bugs and pushlog info) is not enabled.
    This boolean is used to enable a ``prepushkey`` hook that prevents
    pushes to keys (bookmarks, tags, etc) whose name is prefixed with that