Bug 1689965 - Part 2: Use relative path in order to avoid OS-specific description around getting path to the file. r=sylvestre
authorTooru Fujisawa <arai_a@mac.com>
Fri, 20 Aug 2021 04:57:12 +0000
changeset 589401 db611ca2817e6ff9776f4d7cd56ef6231325bcc7
parent 589400 15fe03027a3df9f1cfbdb061e62c93caffa21c0f
child 589402 ac92e6828c49901f864e4a073d209c19629dc254
push id38721
push userarchaeopteryx@coole-files.de
push dateFri, 20 Aug 2021 09:57:55 +0000
treeherdermozilla-central@1e6d20eb3a01 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewerssylvestre
bugs1689965
milestone93.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 1689965 - Part 2: Use relative path in order to avoid OS-specific description around getting path to the file. r=sylvestre Depends on D123059 Differential Revision: https://phabricator.services.mozilla.com/D123060
docs/contributing/vcs/mercurial_bundles.rst
--- a/docs/contributing/vcs/mercurial_bundles.rst
+++ b/docs/contributing/vcs/mercurial_bundles.rst
@@ -26,22 +26,22 @@ 1. Initialize a new repository (in a dir
 
 .. code-block:: shell
 
                mkdir mozilla-central
                hg init mozilla-central
 
 2. Un-bundle the bundle file to that repository:
 
-On Linux/Mac click on the properties of the file and you can find the path. In case the name of the file is not bundle.hg rename it.
+Move the bundle file next to ``mozilla-central`` directory, and rename it to ``bundle.hg``.
 
 .. code-block:: shell
 
                cd mozilla-central
-               hg unbundle /path/to/your/bundle.hg
+               hg unbundle ../bundle.hg
 
 Get comfortable. Grab a coffee (or your favorite tasty beverage). Maybe a nap. This unbundling process is going to take quite a lot of time.
 
 3. Create the repository's config file ``.hg/hgrc``, and add the following lines, so that Mercurial will automatically know where to pull changes from future updates. You can open the template config file in your editor by running ``hg config --local --edit`` or ``EDITOR=<editor-of-your-choice> hg config --local --edit``
 
 .. code-block:: shell
 
                [paths]