2 files changed, 4 insertions, 4 deletions
diff --git a/docs/internal-fs-layout.md b/docs/internal-fs-layout.md
index b06e898f..5e8690b8 100644
--- a/docs/internal-fs-layout.md
+++ b/docs/internal-fs-layout.md
@@ -34,7 +34,7 @@ For example, if you want to change the manifest branch, you can simply run
    It tracks the git repository at `REPO_URL` using the `REPO_REV` branch.
    Those are specified at `repo init` time using the `--repo-url=<REPO_URL>`
-    and `--repo-branch=<REPO_REV>` options.
+    and `--repo-rev=<REPO_REV>` options.
    Any changes made to this directory will usually be automatically discarded
    by repo itself when it checks for updates.  If you want to update to the
diff --git a/docs/release-process.md b/docs/release-process.md
index 121c3bf1..93a0f3e0 100644
--- a/docs/release-process.md
+++ b/docs/release-process.md
@@ -49,11 +49,11 @@ control how repo finds updates:
 *   `--repo-url`: This tells repo where to clone the full repo project itself.
    It defaults to the official project (`REPO_URL` in the launcher script).
-*   `--repo-branch`: This tells repo which branch to use for the full project.
+*   `--repo-rev`: This tells repo which branch to use for the full project.
    It defaults to the `stable` branch (`REPO_REV` in the launcher script).
 Whenever `repo sync` is run, repo will check to see if an update is available.
-It fetches the latest repo-branch from the repo-url.
+It fetches the latest repo-rev from the repo-url.
 Then it verifies that the latest commit in the branch has a valid signed tag
 using `git tag -v` (which uses gpg).
 If the tag is valid, then repo will update its internal checkout to it.
@@ -91,7 +91,7 @@ When you want to create a new release, you'll need to select a good version and
 create a signed tag using a key registered in repo itself.
 Typically we just tag the latest version of the `master` branch.
 The tag could be pushed now, but it won't be used by clients normally (since the
-default `repo-branch` setting is `stable`).
+default `repo-rev` setting is `stable`).
 This would allow some early testing on systems who explicitly select `master`.
 ### Creating a signed tag

diff --git a/docs/internal-fs-layout.md b/docs/internal-fs-layout.md index b06e898f..5e8690b8 100644 --- a/docs/internal-fs-layout.md +++ b/docs/internal-fs-layout.md
@@ -34,7 +34,7 @@ For example, if you want to change the manifest branch, you can simply run
34		34
35	It tracks the git repository at `REPO_URL` using the `REPO_REV` branch.	35	It tracks the git repository at `REPO_URL` using the `REPO_REV` branch.
36	Those are specified at `repo init` time using the `--repo-url=<REPO_URL>`	36	Those are specified at `repo init` time using the `--repo-url=<REPO_URL>`
37	and `--repo-branch=<REPO_REV>` options.	37	and `--repo-rev=<REPO_REV>` options.
38		38
39	Any changes made to this directory will usually be automatically discarded	39	Any changes made to this directory will usually be automatically discarded
40	by repo itself when it checks for updates. If you want to update to the	40	by repo itself when it checks for updates. If you want to update to the


diff --git a/docs/release-process.md b/docs/release-process.md index 121c3bf1..93a0f3e0 100644 --- a/docs/release-process.md +++ b/docs/release-process.md
@@ -49,11 +49,11 @@ control how repo finds updates:
49		49
50	* `--repo-url`: This tells repo where to clone the full repo project itself.	50	* `--repo-url`: This tells repo where to clone the full repo project itself.
51	It defaults to the official project (`REPO_URL` in the launcher script).	51	It defaults to the official project (`REPO_URL` in the launcher script).
52	* `--repo-branch`: This tells repo which branch to use for the full project.	52	* `--repo-rev`: This tells repo which branch to use for the full project.
53	It defaults to the `stable` branch (`REPO_REV` in the launcher script).	53	It defaults to the `stable` branch (`REPO_REV` in the launcher script).
54		54
55	Whenever `repo sync` is run, repo will check to see if an update is available.	55	Whenever `repo sync` is run, repo will check to see if an update is available.
56	It fetches the latest repo-branch from the repo-url.	56	It fetches the latest repo-rev from the repo-url.
57	Then it verifies that the latest commit in the branch has a valid signed tag	57	Then it verifies that the latest commit in the branch has a valid signed tag
58	using `git tag -v` (which uses gpg).	58	using `git tag -v` (which uses gpg).
59	If the tag is valid, then repo will update its internal checkout to it.	59	If the tag is valid, then repo will update its internal checkout to it.
@@ -91,7 +91,7 @@ When you want to create a new release, you'll need to select a good version and
91	create a signed tag using a key registered in repo itself.	91	create a signed tag using a key registered in repo itself.
92	Typically we just tag the latest version of the `master` branch.	92	Typically we just tag the latest version of the `master` branch.
93	The tag could be pushed now, but it won't be used by clients normally (since the	93	The tag could be pushed now, but it won't be used by clients normally (since the
94	default `repo-branch` setting is `stable`).	94	default `repo-rev` setting is `stable`).
95	This would allow some early testing on systems who explicitly select `master`.	95	This would allow some early testing on systems who explicitly select `master`.
96		96
97	### Creating a signed tag	97	### Creating a signed tag