summaryrefslogtreecommitdiffstats
path: root/man
diff options
context:
space:
mode:
authorKaushik Lingarkar <kaushik.lingarkar@linaro.org>2024-09-05 15:34:48 -0700
committerLUCI <gerrit-scoped@luci-project-accounts.iam.gserviceaccount.com>2024-09-26 00:52:28 +0000
commitd7ebdf56be6095338ea37bd4b52533c5bd7774e7 (patch)
treee6db62fd873e70bb0453791a69f8772f9d567a0c /man
parentfabab4e24527fca9b6b4a0c64607524b1890c609 (diff)
downloadgit-repo-d7ebdf56be6095338ea37bd4b52533c5bd7774e7.tar.gz
init: add --manifest-upstream-branch
When a sha1 is provided to '--manifest-branch', the ref which is expected to contain that sha1 can be provided using the new '--manifest-upstream-branch' option. This is useful with '--current-branch' to avoid having to sync all heads and tags, or with a commit that comes from a non-head/tag ref (like a Gerrit change ref). Change-Id: I46a3e255ca69ed9e809039e58b0c163e02af94ef Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/436717 Reviewed-by: Josip Sokcevic <sokcevic@google.com> Commit-Queue: Kaushik Lingarkar <kaushik.lingarkar@linaro.org> Tested-by: Kaushik Lingarkar <kaushik.lingarkar@linaro.org>
Diffstat (limited to 'man')
-rw-r--r--man/repo-init.111
1 files changed, 10 insertions, 1 deletions
diff --git a/man/repo-init.1 b/man/repo-init.1
index cf93de1f..37411752 100644
--- a/man/repo-init.1
+++ b/man/repo-init.1
@@ -1,5 +1,5 @@
1.\" DO NOT MODIFY THIS FILE! It was generated by help2man. 1.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
2.TH REPO "1" "October 2022" "repo init" "Repo Manual" 2.TH REPO "1" "September 2024" "repo init" "Repo Manual"
3.SH NAME 3.SH NAME
4repo \- repo init - manual page for repo init 4repo \- repo init - manual page for repo init
5.SH SYNOPSIS 5.SH SYNOPSIS
@@ -28,6 +28,11 @@ manifest repository location
28\fB\-b\fR REVISION, \fB\-\-manifest\-branch\fR=\fI\,REVISION\/\fR 28\fB\-b\fR REVISION, \fB\-\-manifest\-branch\fR=\fI\,REVISION\/\fR
29manifest branch or revision (use HEAD for default) 29manifest branch or revision (use HEAD for default)
30.TP 30.TP
31\fB\-\-manifest\-upstream\-branch\fR=\fI\,BRANCH\/\fR
32when a commit is provided to \fB\-\-manifest\-branch\fR, this
33is the name of the git ref in which the commit can be
34found
35.TP
31\fB\-m\fR NAME.xml, \fB\-\-manifest\-name\fR=\fI\,NAME\/\fR.xml 36\fB\-m\fR NAME.xml, \fB\-\-manifest\-name\fR=\fI\,NAME\/\fR.xml
32initial manifest file 37initial manifest file
33.TP 38.TP
@@ -163,6 +168,10 @@ The optional \fB\-b\fR argument can be used to select the manifest branch to che
163and use. If no branch is specified, the remote's default branch is used. This is 168and use. If no branch is specified, the remote's default branch is used. This is
164equivalent to using \fB\-b\fR HEAD. 169equivalent to using \fB\-b\fR HEAD.
165.PP 170.PP
171The optional \fB\-\-manifest\-upstream\-branch\fR argument can be used when a commit is
172provided to \fB\-\-manifest\-branch\fR (or \fB\-b\fR), to specify the name of the git ref in
173which the commit can be found.
174.PP
166The optional \fB\-m\fR argument can be used to specify an alternate manifest to be 175The optional \fB\-m\fR argument can be used to specify an alternate manifest to be
167used. If no manifest is specified, the manifest default.xml will be used. 176used. If no manifest is specified, the manifest default.xml will be used.
168.PP 177.PP