summaryrefslogtreecommitdiffstats
path: root/man
diff options
context:
space:
mode:
Diffstat (limited to 'man')
-rw-r--r--man/repo-abandon.136
-rw-r--r--man/repo-branch.11
-rw-r--r--man/repo-branches.159
-rw-r--r--man/repo-checkout.136
-rw-r--r--man/repo-cherry-pick.128
-rw-r--r--man/repo-diff.135
-rw-r--r--man/repo-diffmanifests.161
-rw-r--r--man/repo-download.144
-rw-r--r--man/repo-forall.1128
-rw-r--r--man/repo-gitc-delete.131
-rw-r--r--man/repo-gitc-init.1150
-rw-r--r--man/repo-grep.1119
-rw-r--r--man/repo-help.133
-rw-r--r--man/repo-info.140
-rw-r--r--man/repo-init.1170
-rw-r--r--man/repo-list.161
-rw-r--r--man/repo-manifest.1548
-rw-r--r--man/repo-overview.139
-rw-r--r--man/repo-prune.128
-rw-r--r--man/repo-rebase.155
-rw-r--r--man/repo-selfupdate.135
-rw-r--r--man/repo-smartsync.1118
-rw-r--r--man/repo-stage.130
-rw-r--r--man/repo-start.141
-rw-r--r--man/repo-status.198
-rw-r--r--man/repo-sync.1209
-rw-r--r--man/repo-upload.1175
-rw-r--r--man/repo-version.124
-rw-r--r--man/repo.1133
29 files changed, 2565 insertions, 0 deletions
diff --git a/man/repo-abandon.1 b/man/repo-abandon.1
new file mode 100644
index 00000000..b3c0422f
--- /dev/null
+++ b/man/repo-abandon.1
@@ -0,0 +1,36 @@
1.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
2.TH REPO "1" "July 2021" "repo abandon" "Repo Manual"
3.SH NAME
4repo \- repo abandon - manual page for repo abandon
5.SH SYNOPSIS
6.B repo
7\fI\,abandon \/\fR[\fI\,--all | <branchname>\/\fR] [\fI\,<project>\/\fR...]
8.SH DESCRIPTION
9Summary
10.PP
11Permanently abandon a development branch
12.PP
13This subcommand permanently abandons a development branch by
14deleting it (and all its history) from your local repository.
15.PP
16It is equivalent to "git branch \fB\-D\fR <branchname>".
17.SH OPTIONS
18.TP
19\fB\-h\fR, \fB\-\-help\fR
20show this help message and exit
21.TP
22\fB\-j\fR JOBS, \fB\-\-jobs\fR=\fI\,JOBS\/\fR
23number of jobs to run in parallel (default: based on
24number of CPU cores)
25.TP
26\fB\-\-all\fR
27delete all branches in all projects
28.SS Logging options:
29.TP
30\fB\-v\fR, \fB\-\-verbose\fR
31show all output
32.TP
33\fB\-q\fR, \fB\-\-quiet\fR
34only show errors
35.PP
36Run `repo help abandon` to view the detailed manual.
diff --git a/man/repo-branch.1 b/man/repo-branch.1
new file mode 100644
index 00000000..854ee98b
--- /dev/null
+++ b/man/repo-branch.1
@@ -0,0 +1 @@
.so man1/repo-branches.1 \ No newline at end of file
diff --git a/man/repo-branches.1 b/man/repo-branches.1
new file mode 100644
index 00000000..7fe0b02d
--- /dev/null
+++ b/man/repo-branches.1
@@ -0,0 +1,59 @@
1.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
2.TH REPO "1" "July 2021" "repo branches" "Repo Manual"
3.SH NAME
4repo \- repo branches - manual page for repo branches
5.SH SYNOPSIS
6.B repo
7\fI\,branches \/\fR[\fI\,<project>\/\fR...]
8.SH DESCRIPTION
9Summary
10.PP
11View current topic branches
12.PP
13Summarizes the currently available topic branches.
14.PP
15# Branch Display
16.PP
17The branch display output by this command is organized into four
18columns of information; for example:
19.TP
20*P nocolor
21| in repo
22.TP
23repo2
24|
25.PP
26The first column contains a * if the branch is the currently
27checked out branch in any of the specified projects, or a blank
28if no project has the branch checked out.
29.PP
30The second column contains either blank, p or P, depending upon
31the upload status of the branch.
32.IP
33(blank): branch not yet published by repo upload
34.IP
35P: all commits were published by repo upload
36p: only some commits were published by repo upload
37.PP
38The third column contains the branch name.
39.PP
40The fourth column (after the | separator) lists the projects that
41the branch appears in, or does not appear in. If no project list
42is shown, then the branch appears in all projects.
43.SH OPTIONS
44.TP
45\fB\-h\fR, \fB\-\-help\fR
46show this help message and exit
47.TP
48\fB\-j\fR JOBS, \fB\-\-jobs\fR=\fI\,JOBS\/\fR
49number of jobs to run in parallel (default: based on
50number of CPU cores)
51.SS Logging options:
52.TP
53\fB\-v\fR, \fB\-\-verbose\fR
54show all output
55.TP
56\fB\-q\fR, \fB\-\-quiet\fR
57only show errors
58.PP
59Run `repo help branches` to view the detailed manual.
diff --git a/man/repo-checkout.1 b/man/repo-checkout.1
new file mode 100644
index 00000000..6dd3e6ca
--- /dev/null
+++ b/man/repo-checkout.1
@@ -0,0 +1,36 @@
1.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
2.TH REPO "1" "July 2021" "repo checkout" "Repo Manual"
3.SH NAME
4repo \- repo checkout - manual page for repo checkout
5.SH SYNOPSIS
6.B repo
7\fI\,checkout <branchname> \/\fR[\fI\,<project>\/\fR...]
8.SH DESCRIPTION
9Summary
10.PP
11Checkout a branch for development
12.SH OPTIONS
13.TP
14\fB\-h\fR, \fB\-\-help\fR
15show this help message and exit
16.TP
17\fB\-j\fR JOBS, \fB\-\-jobs\fR=\fI\,JOBS\/\fR
18number of jobs to run in parallel (default: based on
19number of CPU cores)
20.SS Logging options:
21.TP
22\fB\-v\fR, \fB\-\-verbose\fR
23show all output
24.TP
25\fB\-q\fR, \fB\-\-quiet\fR
26only show errors
27.PP
28Run `repo help checkout` to view the detailed manual.
29.SH DETAILS
30.PP
31The 'repo checkout' command checks out an existing branch that was previously
32created by 'repo start'.
33.PP
34The command is equivalent to:
35.IP
36repo forall [<project>...] \fB\-c\fR git checkout <branchname>
diff --git a/man/repo-cherry-pick.1 b/man/repo-cherry-pick.1
new file mode 100644
index 00000000..e7716c55
--- /dev/null
+++ b/man/repo-cherry-pick.1
@@ -0,0 +1,28 @@
1.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
2.TH REPO "1" "July 2021" "repo cherry-pick" "Repo Manual"
3.SH NAME
4repo \- repo cherry-pick - manual page for repo cherry-pick
5.SH SYNOPSIS
6.B repo
7\fI\,cherry-pick <sha1>\/\fR
8.SH DESCRIPTION
9Summary
10.PP
11Cherry\-pick a change.
12.SH OPTIONS
13.TP
14\fB\-h\fR, \fB\-\-help\fR
15show this help message and exit
16.SS Logging options:
17.TP
18\fB\-v\fR, \fB\-\-verbose\fR
19show all output
20.TP
21\fB\-q\fR, \fB\-\-quiet\fR
22only show errors
23.PP
24Run `repo help cherry\-pick` to view the detailed manual.
25.SH DETAILS
26.PP
27\&'repo cherry\-pick' cherry\-picks a change from one branch to another. The change
28id will be updated, and a reference to the old change id will be added.
diff --git a/man/repo-diff.1 b/man/repo-diff.1
new file mode 100644
index 00000000..890f8d22
--- /dev/null
+++ b/man/repo-diff.1
@@ -0,0 +1,35 @@
1.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
2.TH REPO "1" "July 2021" "repo diff" "Repo Manual"
3.SH NAME
4repo \- repo diff - manual page for repo diff
5.SH SYNOPSIS
6.B repo
7\fI\,diff \/\fR[\fI\,<project>\/\fR...]
8.SH DESCRIPTION
9Summary
10.PP
11Show changes between commit and working tree
12.PP
13The \fB\-u\fR option causes 'repo diff' to generate diff output with file paths
14relative to the repository root, so the output can be applied
15to the Unix 'patch' command.
16.SH OPTIONS
17.TP
18\fB\-h\fR, \fB\-\-help\fR
19show this help message and exit
20.TP
21\fB\-j\fR JOBS, \fB\-\-jobs\fR=\fI\,JOBS\/\fR
22number of jobs to run in parallel (default: based on
23number of CPU cores)
24.TP
25\fB\-u\fR, \fB\-\-absolute\fR
26paths are relative to the repository root
27.SS Logging options:
28.TP
29\fB\-v\fR, \fB\-\-verbose\fR
30show all output
31.TP
32\fB\-q\fR, \fB\-\-quiet\fR
33only show errors
34.PP
35Run `repo help diff` to view the detailed manual.
diff --git a/man/repo-diffmanifests.1 b/man/repo-diffmanifests.1
new file mode 100644
index 00000000..add50f17
--- /dev/null
+++ b/man/repo-diffmanifests.1
@@ -0,0 +1,61 @@
1.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
2.TH REPO "1" "July 2021" "repo diffmanifests" "Repo Manual"
3.SH NAME
4repo \- repo diffmanifests - manual page for repo diffmanifests
5.SH SYNOPSIS
6.B repo
7\fI\,diffmanifests manifest1.xml \/\fR[\fI\,manifest2.xml\/\fR] [\fI\,options\/\fR]
8.SH DESCRIPTION
9Summary
10.PP
11Manifest diff utility
12.SH OPTIONS
13.TP
14\fB\-h\fR, \fB\-\-help\fR
15show this help message and exit
16.TP
17\fB\-\-raw\fR
18display raw diff
19.TP
20\fB\-\-no\-color\fR
21does not display the diff in color
22.TP
23\fB\-\-pretty\-format=\fR<FORMAT>
24print the log using a custom git pretty format string
25.SS Logging options:
26.TP
27\fB\-v\fR, \fB\-\-verbose\fR
28show all output
29.TP
30\fB\-q\fR, \fB\-\-quiet\fR
31only show errors
32.PP
33Run `repo help diffmanifests` to view the detailed manual.
34.SH DETAILS
35.PP
36The repo diffmanifests command shows differences between project revisions of
37manifest1 and manifest2. if manifest2 is not specified, current manifest.xml
38will be used instead. Both absolute and relative paths may be used for
39manifests. Relative paths start from project's ".repo/manifests" folder.
40.PP
41The \fB\-\-raw\fR option Displays the diff in a way that facilitates parsing, the
42project pattern will be <status> <path> <revision from> [<revision to>] and the
43commit pattern will be <status> <onelined log> with status values respectively :
44.IP
45A = Added project
46R = Removed project
47C = Changed project
48U = Project with unreachable revision(s) (revision(s) not found)
49.PP
50for project, and
51.IP
52A = Added commit
53R = Removed commit
54.PP
55for a commit.
56.PP
57Only changed projects may contain commits, and commit status always starts with
58a space, and are part of last printed project. Unreachable revisions may occur
59if project is not up to date or if repo has not been initialized with all the
60groups, in which case some projects won't be synced and their revisions won't be
61found.
diff --git a/man/repo-download.1 b/man/repo-download.1
new file mode 100644
index 00000000..cf7f767d
--- /dev/null
+++ b/man/repo-download.1
@@ -0,0 +1,44 @@
1.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
2.TH REPO "1" "July 2021" "repo download" "Repo Manual"
3.SH NAME
4repo \- repo download - manual page for repo download
5.SH SYNOPSIS
6.B repo
7\fI\,download {\/\fR[\fI\,project\/\fR] \fI\,change\/\fR[\fI\,/patchset\/\fR]\fI\,}\/\fR...
8.SH DESCRIPTION
9Summary
10.PP
11Download and checkout a change
12.SH OPTIONS
13.TP
14\fB\-h\fR, \fB\-\-help\fR
15show this help message and exit
16.TP
17\fB\-b\fR BRANCH, \fB\-\-branch\fR=\fI\,BRANCH\/\fR
18create a new branch first
19.TP
20\fB\-c\fR, \fB\-\-cherry\-pick\fR
21cherry\-pick instead of checkout
22.TP
23\fB\-x\fR, \fB\-\-record\-origin\fR
24pass \fB\-x\fR when cherry\-picking
25.TP
26\fB\-r\fR, \fB\-\-revert\fR
27revert instead of checkout
28.TP
29\fB\-f\fR, \fB\-\-ff\-only\fR
30force fast\-forward merge
31.SS Logging options:
32.TP
33\fB\-v\fR, \fB\-\-verbose\fR
34show all output
35.TP
36\fB\-q\fR, \fB\-\-quiet\fR
37only show errors
38.PP
39Run `repo help download` to view the detailed manual.
40.SH DETAILS
41.PP
42The 'repo download' command downloads a change from the review system and makes
43it available in your project's local working directory. If no project is
44specified try to use current directory as a project.
diff --git a/man/repo-forall.1 b/man/repo-forall.1
new file mode 100644
index 00000000..eb2ad57b
--- /dev/null
+++ b/man/repo-forall.1
@@ -0,0 +1,128 @@
1.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
2.TH REPO "1" "July 2021" "repo forall" "Repo Manual"
3.SH NAME
4repo \- repo forall - manual page for repo forall
5.SH SYNOPSIS
6.B repo
7\fI\,forall \/\fR[\fI\,<project>\/\fR...] \fI\,-c <command> \/\fR[\fI\,<arg>\/\fR...]
8.SH DESCRIPTION
9Summary
10.PP
11Run a shell command in each project
12.PP
13repo forall \fB\-r\fR str1 [str2] ... \fB\-c\fR <command> [<arg>...]
14.SH OPTIONS
15.TP
16\fB\-h\fR, \fB\-\-help\fR
17show this help message and exit
18.TP
19\fB\-j\fR JOBS, \fB\-\-jobs\fR=\fI\,JOBS\/\fR
20number of jobs to run in parallel (default: based on
21number of CPU cores)
22.TP
23\fB\-r\fR, \fB\-\-regex\fR
24execute the command only on projects matching regex or
25wildcard expression
26.TP
27\fB\-i\fR, \fB\-\-inverse\-regex\fR
28execute the command only on projects not matching
29regex or wildcard expression
30.TP
31\fB\-g\fR GROUPS, \fB\-\-groups\fR=\fI\,GROUPS\/\fR
32execute the command only on projects matching the
33specified groups
34.TP
35\fB\-c\fR, \fB\-\-command\fR
36command (and arguments) to execute
37.TP
38\fB\-e\fR, \fB\-\-abort\-on\-errors\fR
39abort if a command exits unsuccessfully
40.TP
41\fB\-\-ignore\-missing\fR
42silently skip & do not exit non\-zero due missing
43checkouts
44.TP
45\fB\-\-interactive\fR
46force interactive usage
47.SS Logging options:
48.TP
49\fB\-v\fR, \fB\-\-verbose\fR
50show all output
51.TP
52\fB\-q\fR, \fB\-\-quiet\fR
53only show errors
54.TP
55\fB\-p\fR
56show project headers before output
57.PP
58Run `repo help forall` to view the detailed manual.
59.SH DETAILS
60.PP
61Executes the same shell command in each project.
62.PP
63The \fB\-r\fR option allows running the command only on projects matching regex or
64wildcard expression.
65.PP
66By default, projects are processed non\-interactively in parallel. If you want to
67run interactive commands, make sure to pass \fB\-\-interactive\fR to force \fB\-\-jobs\fR 1.
68While the processing order of projects is not guaranteed, the order of project
69output is stable.
70.PP
71Output Formatting
72.PP
73The \fB\-p\fR option causes 'repo forall' to bind pipes to the command's stdin, stdout
74and stderr streams, and pipe all output into a continuous stream that is
75displayed in a single pager session. Project headings are inserted before the
76output of each command is displayed. If the command produces no output in a
77project, no heading is displayed.
78.PP
79The formatting convention used by \fB\-p\fR is very suitable for some types of
80searching, e.g. `repo forall \fB\-p\fR \fB\-c\fR git log \fB\-SFoo\fR` will print all commits that
81add or remove references to Foo.
82.PP
83The \fB\-v\fR option causes 'repo forall' to display stderr messages if a command
84produces output only on stderr. Normally the \fB\-p\fR option causes command output to
85be suppressed until the command produces at least one byte of output on stdout.
86.PP
87Environment
88.PP
89pwd is the project's working directory. If the current client is a mirror
90client, then pwd is the Git repository.
91.PP
92REPO_PROJECT is set to the unique name of the project.
93.PP
94REPO_PATH is the path relative the the root of the client.
95.PP
96REPO_REMOTE is the name of the remote system from the manifest.
97.PP
98REPO_LREV is the name of the revision from the manifest, translated to a local
99tracking branch. If you need to pass the manifest revision to a locally executed
100git command, use REPO_LREV.
101.PP
102REPO_RREV is the name of the revision from the manifest, exactly as written in
103the manifest.
104.PP
105REPO_COUNT is the total number of projects being iterated.
106.PP
107REPO_I is the current (1\-based) iteration count. Can be used in conjunction with
108REPO_COUNT to add a simple progress indicator to your command.
109.PP
110REPO__* are any extra environment variables, specified by the "annotation"
111element under any project element. This can be useful for differentiating trees
112based on user\-specific criteria, or simply annotating tree details.
113.PP
114shell positional arguments ($1, $2, .., $#) are set to any arguments following
115<command>.
116.PP
117Example: to list projects:
118.IP
119repo forall \fB\-c\fR 'echo $REPO_PROJECT'
120.PP
121Notice that $REPO_PROJECT is quoted to ensure it is expanded in the context of
122running <command> instead of in the calling shell.
123.PP
124Unless \fB\-p\fR is used, stdin, stdout, stderr are inherited from the terminal and are
125not redirected.
126.PP
127If \fB\-e\fR is used, when a command exits unsuccessfully, 'repo forall' will abort
128without iterating through the remaining projects.
diff --git a/man/repo-gitc-delete.1 b/man/repo-gitc-delete.1
new file mode 100644
index 00000000..c84c6e45
--- /dev/null
+++ b/man/repo-gitc-delete.1
@@ -0,0 +1,31 @@
1.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
2.TH REPO "1" "July 2021" "repo gitc-delete" "Repo Manual"
3.SH NAME
4repo \- repo gitc-delete - manual page for repo gitc-delete
5.SH SYNOPSIS
6.B repo
7\fI\,gitc-delete\/\fR
8.SH DESCRIPTION
9Summary
10.PP
11Delete a GITC Client.
12.SH OPTIONS
13.TP
14\fB\-h\fR, \fB\-\-help\fR
15show this help message and exit
16.TP
17\fB\-f\fR, \fB\-\-force\fR
18force the deletion (no prompt)
19.SS Logging options:
20.TP
21\fB\-v\fR, \fB\-\-verbose\fR
22show all output
23.TP
24\fB\-q\fR, \fB\-\-quiet\fR
25only show errors
26.PP
27Run `repo help gitc\-delete` to view the detailed manual.
28.SH DETAILS
29.PP
30This subcommand deletes the current GITC client, deleting the GITC manifest and
31all locally downloaded sources.
diff --git a/man/repo-gitc-init.1 b/man/repo-gitc-init.1
new file mode 100644
index 00000000..9b61866e
--- /dev/null
+++ b/man/repo-gitc-init.1
@@ -0,0 +1,150 @@
1.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
2.TH REPO "1" "September 2021" "repo gitc-init" "Repo Manual"
3.SH NAME
4repo \- repo gitc-init - manual page for repo gitc-init
5.SH SYNOPSIS
6.B repo
7\fI\,gitc-init \/\fR[\fI\,options\/\fR] [\fI\,client name\/\fR]
8.SH DESCRIPTION
9Summary
10.PP
11Initialize a GITC Client.
12.SH OPTIONS
13.TP
14\fB\-h\fR, \fB\-\-help\fR
15show this help message and exit
16.SS Logging options:
17.TP
18\fB\-v\fR, \fB\-\-verbose\fR
19show all output
20.TP
21\fB\-q\fR, \fB\-\-quiet\fR
22only show errors
23.SS Manifest options:
24.TP
25\fB\-u\fR URL, \fB\-\-manifest\-url\fR=\fI\,URL\/\fR
26manifest repository location
27.TP
28\fB\-b\fR REVISION, \fB\-\-manifest\-branch\fR=\fI\,REVISION\/\fR
29manifest branch or revision (use HEAD for default)
30.TP
31\fB\-m\fR NAME.xml, \fB\-\-manifest\-name\fR=\fI\,NAME\/\fR.xml
32initial manifest file
33.TP
34\fB\-\-standalone\-manifest\fR
35download the manifest as a static file rather then
36create a git checkout of the manifest repo
37.TP
38\fB\-g\fR GROUP, \fB\-\-groups\fR=\fI\,GROUP\/\fR
39restrict manifest projects to ones with specified
40group(s) [default|all|G1,G2,G3|G4,\-G5,\-G6]
41.TP
42\fB\-p\fR PLATFORM, \fB\-\-platform\fR=\fI\,PLATFORM\/\fR
43restrict manifest projects to ones with a specified
44platform group [auto|all|none|linux|darwin|...]
45.TP
46\fB\-\-submodules\fR
47sync any submodules associated with the manifest repo
48.SS Manifest (only) checkout options:
49.TP
50\fB\-\-current\-branch\fR
51fetch only current manifest branch from server
52.TP
53\fB\-\-no\-current\-branch\fR
54fetch all manifest branches from server
55.TP
56\fB\-\-tags\fR
57fetch tags in the manifest
58.TP
59\fB\-\-no\-tags\fR
60don't fetch tags in the manifest
61.SS Checkout modes:
62.TP
63\fB\-\-mirror\fR
64create a replica of the remote repositories rather
65than a client working directory
66.TP
67\fB\-\-archive\fR
68checkout an archive instead of a git repository for
69each project. See git archive.
70.TP
71\fB\-\-worktree\fR
72use git\-worktree to manage projects
73.SS Project checkout optimizations:
74.TP
75\fB\-\-reference\fR=\fI\,DIR\/\fR
76location of mirror directory
77.TP
78\fB\-\-dissociate\fR
79dissociate from reference mirrors after clone
80.TP
81\fB\-\-depth\fR=\fI\,DEPTH\/\fR
82create a shallow clone with given depth; see git clone
83.TP
84\fB\-\-partial\-clone\fR
85perform partial clone (https://gitscm.com/docs/gitrepositorylayout#_code_partialclone_code)
86.TP
87\fB\-\-no\-partial\-clone\fR
88disable use of partial clone (https://gitscm.com/docs/gitrepositorylayout#_code_partialclone_code)
89.TP
90\fB\-\-partial\-clone\-exclude\fR=\fI\,PARTIAL_CLONE_EXCLUDE\/\fR
91exclude the specified projects (a comma\-delimited
92project names) from partial clone (https://gitscm.com/docs/gitrepositorylayout#_code_partialclone_code)
93.TP
94\fB\-\-clone\-filter\fR=\fI\,CLONE_FILTER\/\fR
95filter for use with \fB\-\-partial\-clone\fR [default:
96blob:none]
97.TP
98\fB\-\-use\-superproject\fR
99use the manifest superproject to sync projects
100.TP
101\fB\-\-no\-use\-superproject\fR
102disable use of manifest superprojects
103.TP
104\fB\-\-clone\-bundle\fR
105enable use of \fI\,/clone.bundle\/\fP on HTTP/HTTPS (default if
106not \fB\-\-partial\-clone\fR)
107.TP
108\fB\-\-no\-clone\-bundle\fR
109disable use of \fI\,/clone.bundle\/\fP on HTTP/HTTPS (default if
110\fB\-\-partial\-clone\fR)
111.SS repo Version options:
112.TP
113\fB\-\-repo\-url\fR=\fI\,URL\/\fR
114repo repository location ($REPO_URL)
115.TP
116\fB\-\-repo\-rev\fR=\fI\,REV\/\fR
117repo branch or revision ($REPO_REV)
118.TP
119\fB\-\-no\-repo\-verify\fR
120do not verify repo source code
121.SS Other options:
122.TP
123\fB\-\-config\-name\fR
124Always prompt for name/e\-mail
125.SS GITC options:
126.TP
127\fB\-f\fR MANIFEST_FILE, \fB\-\-manifest\-file\fR=\fI\,MANIFEST_FILE\/\fR
128Optional manifest file to use for this GITC client.
129.TP
130\fB\-c\fR GITC_CLIENT, \fB\-\-gitc\-client\fR=\fI\,GITC_CLIENT\/\fR
131Name of the gitc_client instance to create or modify.
132.PP
133Run `repo help gitc\-init` to view the detailed manual.
134.SH DETAILS
135.PP
136The 'repo gitc\-init' command is ran to initialize a new GITC client for use with
137the GITC file system.
138.PP
139This command will setup the client directory, initialize repo, just like repo
140init does, and then downloads the manifest collection and installs it in the
141\&.repo/directory of the GITC client.
142.PP
143Once this is done, a GITC manifest is generated by pulling the HEAD SHA for each
144project and generates the properly formatted XML file and installs it as
145\&.manifest in the GITC client directory.
146.PP
147The \fB\-c\fR argument is required to specify the GITC client name.
148.PP
149The optional \fB\-f\fR argument can be used to specify the manifest file to use for
150this GITC client.
diff --git a/man/repo-grep.1 b/man/repo-grep.1
new file mode 100644
index 00000000..be410588
--- /dev/null
+++ b/man/repo-grep.1
@@ -0,0 +1,119 @@
1.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
2.TH REPO "1" "July 2021" "repo grep" "Repo Manual"
3.SH NAME
4repo \- repo grep - manual page for repo grep
5.SH SYNOPSIS
6.B repo
7\fI\,grep {pattern | -e pattern} \/\fR[\fI\,<project>\/\fR...]
8.SH DESCRIPTION
9Summary
10.PP
11Print lines matching a pattern
12.SH OPTIONS
13.TP
14\fB\-h\fR, \fB\-\-help\fR
15show this help message and exit
16.TP
17\fB\-j\fR JOBS, \fB\-\-jobs\fR=\fI\,JOBS\/\fR
18number of jobs to run in parallel (default: based on
19number of CPU cores)
20.SS Logging options:
21.TP
22\fB\-\-verbose\fR
23show all output
24.TP
25\fB\-q\fR, \fB\-\-quiet\fR
26only show errors
27.SS Sources:
28.TP
29\fB\-\-cached\fR
30Search the index, instead of the work tree
31.TP
32\fB\-r\fR TREEish, \fB\-\-revision\fR=\fI\,TREEish\/\fR
33Search TREEish, instead of the work tree
34.SS Pattern:
35.TP
36\fB\-e\fR PATTERN
37Pattern to search for
38.TP
39\fB\-i\fR, \fB\-\-ignore\-case\fR
40Ignore case differences
41.TP
42\fB\-a\fR, \fB\-\-text\fR
43Process binary files as if they were text
44.TP
45\fB\-I\fR
46Don't match the pattern in binary files
47.TP
48\fB\-w\fR, \fB\-\-word\-regexp\fR
49Match the pattern only at word boundaries
50.TP
51\fB\-v\fR, \fB\-\-invert\-match\fR
52Select non\-matching lines
53.TP
54\fB\-G\fR, \fB\-\-basic\-regexp\fR
55Use POSIX basic regexp for patterns (default)
56.TP
57\fB\-E\fR, \fB\-\-extended\-regexp\fR
58Use POSIX extended regexp for patterns
59.TP
60\fB\-F\fR, \fB\-\-fixed\-strings\fR
61Use fixed strings (not regexp) for pattern
62.SS Pattern Grouping:
63.TP
64\fB\-\-all\-match\fR
65Limit match to lines that have all patterns
66.TP
67\fB\-\-and\fR, \fB\-\-or\fR, \fB\-\-not\fR
68Boolean operators to combine patterns
69.TP
70\-(, \-)
71Boolean operator grouping
72.SS Output:
73.TP
74\fB\-n\fR
75Prefix the line number to matching lines
76.TP
77\fB\-C\fR CONTEXT
78Show CONTEXT lines around match
79.TP
80\fB\-B\fR CONTEXT
81Show CONTEXT lines before match
82.TP
83\fB\-A\fR CONTEXT
84Show CONTEXT lines after match
85.TP
86\fB\-l\fR, \fB\-\-name\-only\fR, \fB\-\-files\-with\-matches\fR
87Show only file names containing matching lines
88.TP
89\fB\-L\fR, \fB\-\-files\-without\-match\fR
90Show only file names not containing matching lines
91.PP
92Run `repo help grep` to view the detailed manual.
93.SH DETAILS
94.PP
95Search for the specified patterns in all project files.
96.PP
97Boolean Options
98.PP
99The following options can appear as often as necessary to express the pattern to
100locate:
101.HP
102\fB\-e\fR PATTERN
103.HP
104\fB\-\-and\fR, \fB\-\-or\fR, \fB\-\-not\fR, \-(, \-)
105.PP
106Further, the \fB\-r\fR/\-\-revision option may be specified multiple times in order to
107scan multiple trees. If the same file matches in more than one tree, only the
108first result is reported, prefixed by the revision name it was found under.
109.PP
110Examples
111.PP
112Look for a line that has '#define' and either 'MAX_PATH or 'PATH_MAX':
113.IP
114repo grep \fB\-e\fR '#define' \fB\-\-and\fR \-\e( \fB\-e\fR MAX_PATH \fB\-e\fR PATH_MAX \e)
115.PP
116Look for a line that has 'NODE' or 'Unexpected' in files that contain a line
117that matches both expressions:
118.IP
119repo grep \fB\-\-all\-match\fR \fB\-e\fR NODE \fB\-e\fR Unexpected
diff --git a/man/repo-help.1 b/man/repo-help.1
new file mode 100644
index 00000000..d6da3c51
--- /dev/null
+++ b/man/repo-help.1
@@ -0,0 +1,33 @@
1.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
2.TH REPO "1" "July 2021" "repo help" "Repo Manual"
3.SH NAME
4repo \- repo help - manual page for repo help
5.SH SYNOPSIS
6.B repo
7\fI\,help \/\fR[\fI\,--all|command\/\fR]
8.SH DESCRIPTION
9Summary
10.PP
11Display detailed help on a command
12.SH OPTIONS
13.TP
14\fB\-h\fR, \fB\-\-help\fR
15show this help message and exit
16.TP
17\fB\-a\fR, \fB\-\-all\fR
18show the complete list of commands
19.TP
20\fB\-\-help\-all\fR
21show the \fB\-\-help\fR of all commands
22.SS Logging options:
23.TP
24\fB\-v\fR, \fB\-\-verbose\fR
25show all output
26.TP
27\fB\-q\fR, \fB\-\-quiet\fR
28only show errors
29.PP
30Run `repo help help` to view the detailed manual.
31.SH DETAILS
32.PP
33Displays detailed usage information about a command.
diff --git a/man/repo-info.1 b/man/repo-info.1
new file mode 100644
index 00000000..cf7c17b8
--- /dev/null
+++ b/man/repo-info.1
@@ -0,0 +1,40 @@
1.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
2.TH REPO "1" "July 2021" "repo info" "Repo Manual"
3.SH NAME
4repo \- repo info - manual page for repo info
5.SH SYNOPSIS
6.B repo
7\fI\,info \/\fR[\fI\,-dl\/\fR] [\fI\,-o \/\fR[\fI\,-c\/\fR]] [\fI\,<project>\/\fR...]
8.SH DESCRIPTION
9Summary
10.PP
11Get info on the manifest branch, current branch or unmerged branches
12.SH OPTIONS
13.TP
14\fB\-h\fR, \fB\-\-help\fR
15show this help message and exit
16.TP
17\fB\-d\fR, \fB\-\-diff\fR
18show full info and commit diff including remote
19branches
20.TP
21\fB\-o\fR, \fB\-\-overview\fR
22show overview of all local commits
23.TP
24\fB\-c\fR, \fB\-\-current\-branch\fR
25consider only checked out branches
26.TP
27\fB\-\-no\-current\-branch\fR
28consider all local branches
29.TP
30\fB\-l\fR, \fB\-\-local\-only\fR
31disable all remote operations
32.SS Logging options:
33.TP
34\fB\-v\fR, \fB\-\-verbose\fR
35show all output
36.TP
37\fB\-q\fR, \fB\-\-quiet\fR
38only show errors
39.PP
40Run `repo help info` to view the detailed manual.
diff --git a/man/repo-init.1 b/man/repo-init.1
new file mode 100644
index 00000000..9957b64d
--- /dev/null
+++ b/man/repo-init.1
@@ -0,0 +1,170 @@
1.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
2.TH REPO "1" "September 2021" "repo init" "Repo Manual"
3.SH NAME
4repo \- repo init - manual page for repo init
5.SH SYNOPSIS
6.B repo
7\fI\,init \/\fR[\fI\,options\/\fR] [\fI\,manifest url\/\fR]
8.SH DESCRIPTION
9Summary
10.PP
11Initialize a repo client checkout in the current directory
12.SH OPTIONS
13.TP
14\fB\-h\fR, \fB\-\-help\fR
15show this help message and exit
16.SS Logging options:
17.TP
18\fB\-v\fR, \fB\-\-verbose\fR
19show all output
20.TP
21\fB\-q\fR, \fB\-\-quiet\fR
22only show errors
23.SS Manifest options:
24.TP
25\fB\-u\fR URL, \fB\-\-manifest\-url\fR=\fI\,URL\/\fR
26manifest repository location
27.TP
28\fB\-b\fR REVISION, \fB\-\-manifest\-branch\fR=\fI\,REVISION\/\fR
29manifest branch or revision (use HEAD for default)
30.TP
31\fB\-m\fR NAME.xml, \fB\-\-manifest\-name\fR=\fI\,NAME\/\fR.xml
32initial manifest file
33.TP
34\fB\-\-standalone\-manifest\fR
35download the manifest as a static file rather then
36create a git checkout of the manifest repo
37.TP
38\fB\-g\fR GROUP, \fB\-\-groups\fR=\fI\,GROUP\/\fR
39restrict manifest projects to ones with specified
40group(s) [default|all|G1,G2,G3|G4,\-G5,\-G6]
41.TP
42\fB\-p\fR PLATFORM, \fB\-\-platform\fR=\fI\,PLATFORM\/\fR
43restrict manifest projects to ones with a specified
44platform group [auto|all|none|linux|darwin|...]
45.TP
46\fB\-\-submodules\fR
47sync any submodules associated with the manifest repo
48.SS Manifest (only) checkout options:
49.TP
50\fB\-c\fR, \fB\-\-current\-branch\fR
51fetch only current manifest branch from server
52.TP
53\fB\-\-no\-current\-branch\fR
54fetch all manifest branches from server
55.TP
56\fB\-\-tags\fR
57fetch tags in the manifest
58.TP
59\fB\-\-no\-tags\fR
60don't fetch tags in the manifest
61.SS Checkout modes:
62.TP
63\fB\-\-mirror\fR
64create a replica of the remote repositories rather
65than a client working directory
66.TP
67\fB\-\-archive\fR
68checkout an archive instead of a git repository for
69each project. See git archive.
70.TP
71\fB\-\-worktree\fR
72use git\-worktree to manage projects
73.SS Project checkout optimizations:
74.TP
75\fB\-\-reference\fR=\fI\,DIR\/\fR
76location of mirror directory
77.TP
78\fB\-\-dissociate\fR
79dissociate from reference mirrors after clone
80.TP
81\fB\-\-depth\fR=\fI\,DEPTH\/\fR
82create a shallow clone with given depth; see git clone
83.TP
84\fB\-\-partial\-clone\fR
85perform partial clone (https://gitscm.com/docs/gitrepositorylayout#_code_partialclone_code)
86.TP
87\fB\-\-no\-partial\-clone\fR
88disable use of partial clone (https://gitscm.com/docs/gitrepositorylayout#_code_partialclone_code)
89.TP
90\fB\-\-partial\-clone\-exclude\fR=\fI\,PARTIAL_CLONE_EXCLUDE\/\fR
91exclude the specified projects (a comma\-delimited
92project names) from partial clone (https://gitscm.com/docs/gitrepositorylayout#_code_partialclone_code)
93.TP
94\fB\-\-clone\-filter\fR=\fI\,CLONE_FILTER\/\fR
95filter for use with \fB\-\-partial\-clone\fR [default:
96blob:none]
97.TP
98\fB\-\-use\-superproject\fR
99use the manifest superproject to sync projects
100.TP
101\fB\-\-no\-use\-superproject\fR
102disable use of manifest superprojects
103.TP
104\fB\-\-clone\-bundle\fR
105enable use of \fI\,/clone.bundle\/\fP on HTTP/HTTPS (default if
106not \fB\-\-partial\-clone\fR)
107.TP
108\fB\-\-no\-clone\-bundle\fR
109disable use of \fI\,/clone.bundle\/\fP on HTTP/HTTPS (default if
110\fB\-\-partial\-clone\fR)
111.SS repo Version options:
112.TP
113\fB\-\-repo\-url\fR=\fI\,URL\/\fR
114repo repository location ($REPO_URL)
115.TP
116\fB\-\-repo\-rev\fR=\fI\,REV\/\fR
117repo branch or revision ($REPO_REV)
118.TP
119\fB\-\-no\-repo\-verify\fR
120do not verify repo source code
121.SS Other options:
122.TP
123\fB\-\-config\-name\fR
124Always prompt for name/e\-mail
125.PP
126Run `repo help init` to view the detailed manual.
127.SH DETAILS
128.PP
129The 'repo init' command is run once to install and initialize repo. The latest
130repo source code and manifest collection is downloaded from the server and is
131installed in the .repo/ directory in the current working directory.
132.PP
133When creating a new checkout, the manifest URL is the only required setting. It
134may be specified using the \fB\-\-manifest\-url\fR option, or as the first optional
135argument.
136.PP
137The optional \fB\-b\fR argument can be used to select the manifest branch to checkout
138and use. If no branch is specified, the remote's default branch is used. This is
139equivalent to using \fB\-b\fR HEAD.
140.PP
141The optional \fB\-m\fR argument can be used to specify an alternate manifest to be
142used. If no manifest is specified, the manifest default.xml will be used.
143.PP
144If the \fB\-\-standalone\-manifest\fR argument is set, the manifest will be downloaded
145directly from the specified \fB\-\-manifest\-url\fR as a static file (rather than setting
146up a manifest git checkout). With \fB\-\-standalone\-manifest\fR, the manifest will be
147fully static and will not be re\-downloaded during subsesquent `repo init` and
148`repo sync` calls.
149.PP
150The \fB\-\-reference\fR option can be used to point to a directory that has the content
151of a \fB\-\-mirror\fR sync. This will make the working directory use as much data as
152possible from the local reference directory when fetching from the server. This
153will make the sync go a lot faster by reducing data traffic on the network.
154.PP
155The \fB\-\-dissociate\fR option can be used to borrow the objects from the directory
156specified with the \fB\-\-reference\fR option only to reduce network transfer, and stop
157borrowing from them after a first clone is made by making necessary local copies
158of borrowed objects.
159.PP
160The \fB\-\-no\-clone\-bundle\fR option disables any attempt to use \fI\,$URL/clone.bundle\/\fP to
161bootstrap a new Git repository from a resumeable bundle file on a content
162delivery network. This may be necessary if there are problems with the local
163Python HTTP client or proxy configuration, but the Git binary works.
164.PP
165Switching Manifest Branches
166.PP
167To switch to another manifest branch, `repo init \fB\-b\fR otherbranch` may be used in
168an existing client. However, as this only updates the manifest, a subsequent
169`repo sync` (or `repo sync \fB\-d\fR`) is necessary to update the working directory
170files.
diff --git a/man/repo-list.1 b/man/repo-list.1
new file mode 100644
index 00000000..7f85e612
--- /dev/null
+++ b/man/repo-list.1
@@ -0,0 +1,61 @@
1.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
2.TH REPO "1" "July 2021" "repo list" "Repo Manual"
3.SH NAME
4repo \- repo list - manual page for repo list
5.SH SYNOPSIS
6.B repo
7\fI\,list \/\fR[\fI\,-f\/\fR] [\fI\,<project>\/\fR...]
8.SH DESCRIPTION
9Summary
10.PP
11List projects and their associated directories
12.PP
13repo list [\-f] \fB\-r\fR str1 [str2]...
14.SH OPTIONS
15.TP
16\fB\-h\fR, \fB\-\-help\fR
17show this help message and exit
18.TP
19\fB\-r\fR, \fB\-\-regex\fR
20filter the project list based on regex or wildcard
21matching of strings
22.TP
23\fB\-g\fR GROUPS, \fB\-\-groups\fR=\fI\,GROUPS\/\fR
24filter the project list based on the groups the
25project is in
26.TP
27\fB\-a\fR, \fB\-\-all\fR
28show projects regardless of checkout state
29.TP
30\fB\-n\fR, \fB\-\-name\-only\fR
31display only the name of the repository
32.TP
33\fB\-p\fR, \fB\-\-path\-only\fR
34display only the path of the repository
35.TP
36\fB\-f\fR, \fB\-\-fullpath\fR
37display the full work tree path instead of the
38relative path
39.TP
40\fB\-\-relative\-to\fR=\fI\,PATH\/\fR
41display paths relative to this one (default: top of
42repo client checkout)
43.SS Logging options:
44.TP
45\fB\-v\fR, \fB\-\-verbose\fR
46show all output
47.TP
48\fB\-q\fR, \fB\-\-quiet\fR
49only show errors
50.PP
51Run `repo help list` to view the detailed manual.
52.SH DETAILS
53.PP
54List all projects; pass '.' to list the project for the cwd.
55.PP
56By default, only projects that currently exist in the checkout are shown. If you
57want to list all projects (using the specified filter settings), use the \fB\-\-all\fR
58option. If you want to show all projects regardless of the manifest groups, then
59also pass \fB\-\-groups\fR all.
60.PP
61This is similar to running: repo forall \fB\-c\fR 'echo "$REPO_PATH : $REPO_PROJECT"'.
diff --git a/man/repo-manifest.1 b/man/repo-manifest.1
new file mode 100644
index 00000000..be467607
--- /dev/null
+++ b/man/repo-manifest.1
@@ -0,0 +1,548 @@
1.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
2.TH REPO "1" "July 2021" "repo manifest" "Repo Manual"
3.SH NAME
4repo \- repo manifest - manual page for repo manifest
5.SH SYNOPSIS
6.B repo
7\fI\,manifest \/\fR[\fI\,-o {-|NAME.xml}\/\fR] [\fI\,-m MANIFEST.xml\/\fR] [\fI\,-r\/\fR]
8.SH DESCRIPTION
9Summary
10.PP
11Manifest inspection utility
12.SH OPTIONS
13.TP
14\fB\-h\fR, \fB\-\-help\fR
15show this help message and exit
16.TP
17\fB\-r\fR, \fB\-\-revision\-as\-HEAD\fR
18save revisions as current HEAD
19.TP
20\fB\-m\fR NAME.xml, \fB\-\-manifest\-name\fR=\fI\,NAME\/\fR.xml
21temporary manifest to use for this sync
22.TP
23\fB\-\-suppress\-upstream\-revision\fR
24if in \fB\-r\fR mode, do not write the upstream field (only
25of use if the branch names for a sha1 manifest are
26sensitive)
27.TP
28\fB\-\-suppress\-dest\-branch\fR
29if in \fB\-r\fR mode, do not write the dest\-branch field
30(only of use if the branch names for a sha1 manifest
31are sensitive)
32.TP
33\fB\-\-json\fR
34output manifest in JSON format (experimental)
35.TP
36\fB\-\-pretty\fR
37format output for humans to read
38.TP
39\fB\-\-no\-local\-manifests\fR
40ignore local manifests
41.TP
42\fB\-o\fR \-|NAME.xml, \fB\-\-output\-file\fR=\fI\,\-\/\fR|NAME.xml
43file to save the manifest to
44.SS Logging options:
45.TP
46\fB\-v\fR, \fB\-\-verbose\fR
47show all output
48.TP
49\fB\-q\fR, \fB\-\-quiet\fR
50only show errors
51.PP
52Run `repo help manifest` to view the detailed manual.
53.SH DETAILS
54.PP
55With the \fB\-o\fR option, exports the current manifest for inspection. The manifest
56and (if present) local_manifests/ are combined together to produce a single
57manifest file. This file can be stored in a Git repository for use during future
58\&'repo init' invocations.
59.PP
60The \fB\-r\fR option can be used to generate a manifest file with project revisions set
61to the current commit hash. These are known as "revision locked manifests", as
62they don't follow a particular branch. In this case, the 'upstream' attribute is
63set to the ref we were on when the manifest was generated. The 'dest\-branch'
64attribute is set to indicate the remote ref to push changes to via 'repo
65upload'.
66.PP
67repo Manifest Format
68.PP
69A repo manifest describes the structure of a repo client; that is the
70directories that are visible and where they should be obtained from with git.
71.PP
72The basic structure of a manifest is a bare Git repository holding a single
73`default.xml` XML file in the top level directory.
74.PP
75Manifests are inherently version controlled, since they are kept within a Git
76repository. Updates to manifests are automatically obtained by clients during
77`repo sync`.
78.PP
79[TOC]
80.PP
81XML File Format
82.PP
83A manifest XML file (e.g. `default.xml`) roughly conforms to the following DTD:
84.PP
85```xml <!DOCTYPE manifest [
86.TP
87<!ELEMENT manifest (notice?,
88remote*,
89default?,
90manifest\-server?,
91remove\-project*,
92project*,
93extend\-project*,
94repo\-hooks?,
95superproject?,
96contactinfo?,
97include*)>
98.IP
99<!ELEMENT notice (#PCDATA)>
100.IP
101<!ELEMENT remote (annotation*)>
102<!ATTLIST remote name ID #REQUIRED>
103<!ATTLIST remote alias CDATA #IMPLIED>
104<!ATTLIST remote fetch CDATA #REQUIRED>
105<!ATTLIST remote pushurl CDATA #IMPLIED>
106<!ATTLIST remote review CDATA #IMPLIED>
107<!ATTLIST remote revision CDATA #IMPLIED>
108.IP
109<!ELEMENT default EMPTY>
110<!ATTLIST default remote IDREF #IMPLIED>
111<!ATTLIST default revision CDATA #IMPLIED>
112<!ATTLIST default dest\-branch CDATA #IMPLIED>
113<!ATTLIST default upstream CDATA #IMPLIED>
114<!ATTLIST default sync\-j CDATA #IMPLIED>
115<!ATTLIST default sync\-c CDATA #IMPLIED>
116<!ATTLIST default sync\-s CDATA #IMPLIED>
117<!ATTLIST default sync\-tags CDATA #IMPLIED>
118.IP
119<!ELEMENT manifest\-server EMPTY>
120<!ATTLIST manifest\-server url CDATA #REQUIRED>
121.TP
122<!ELEMENT project (annotation*,
123project*,
124copyfile*,
125linkfile*)>
126.TP
127<!ATTLIST project name
128CDATA #REQUIRED>
129.TP
130<!ATTLIST project path
131CDATA #IMPLIED>
132.TP
133<!ATTLIST project remote
134IDREF #IMPLIED>
135.TP
136<!ATTLIST project revision
137CDATA #IMPLIED>
138.IP
139<!ATTLIST project dest\-branch CDATA #IMPLIED>
140<!ATTLIST project groups CDATA #IMPLIED>
141<!ATTLIST project sync\-c CDATA #IMPLIED>
142<!ATTLIST project sync\-s CDATA #IMPLIED>
143<!ATTLIST project sync\-tags CDATA #IMPLIED>
144<!ATTLIST project upstream CDATA #IMPLIED>
145<!ATTLIST project clone\-depth CDATA #IMPLIED>
146<!ATTLIST project force\-path CDATA #IMPLIED>
147.IP
148<!ELEMENT annotation EMPTY>
149<!ATTLIST annotation name CDATA #REQUIRED>
150<!ATTLIST annotation value CDATA #REQUIRED>
151<!ATTLIST annotation keep CDATA "true">
152.IP
153<!ELEMENT copyfile EMPTY>
154<!ATTLIST copyfile src CDATA #REQUIRED>
155<!ATTLIST copyfile dest CDATA #REQUIRED>
156.IP
157<!ELEMENT linkfile EMPTY>
158<!ATTLIST linkfile src CDATA #REQUIRED>
159<!ATTLIST linkfile dest CDATA #REQUIRED>
160.IP
161<!ELEMENT extend\-project EMPTY>
162<!ATTLIST extend\-project name CDATA #REQUIRED>
163<!ATTLIST extend\-project path CDATA #IMPLIED>
164<!ATTLIST extend\-project groups CDATA #IMPLIED>
165<!ATTLIST extend\-project revision CDATA #IMPLIED>
166<!ATTLIST extend\-project remote CDATA #IMPLIED>
167.IP
168<!ELEMENT remove\-project EMPTY>
169<!ATTLIST remove\-project name CDATA #REQUIRED>
170<!ATTLIST remove\-project optional CDATA #IMPLIED>
171.IP
172<!ELEMENT repo\-hooks EMPTY>
173<!ATTLIST repo\-hooks in\-project CDATA #REQUIRED>
174<!ATTLIST repo\-hooks enabled\-list CDATA #REQUIRED>
175.IP
176<!ELEMENT superproject EMPTY>
177<!ATTLIST superproject name CDATA #REQUIRED>
178<!ATTLIST superproject remote IDREF #IMPLIED>
179.IP
180<!ELEMENT contactinfo EMPTY>
181<!ATTLIST contactinfo bugurl CDATA #REQUIRED>
182.IP
183<!ELEMENT include EMPTY>
184<!ATTLIST include name CDATA #REQUIRED>
185<!ATTLIST include groups CDATA #IMPLIED>
186.PP
187]>
188```
189.PP
190For compatibility purposes across repo releases, all unknown elements are
191silently ignored. However, repo reserves all possible names for itself for
192future use. If you want to use custom elements, the `x\-*` namespace is reserved
193for that purpose, and repo guarantees to never allocate any corresponding names.
194.PP
195A description of the elements and their attributes follows.
196.PP
197Element manifest
198.PP
199The root element of the file.
200.PP
201Element notice
202.PP
203Arbitrary text that is displayed to users whenever `repo sync` finishes. The
204content is simply passed through as it exists in the manifest.
205.PP
206Element remote
207.PP
208One or more remote elements may be specified. Each remote element specifies a
209Git URL shared by one or more projects and (optionally) the Gerrit review server
210those projects upload changes through.
211.PP
212Attribute `name`: A short name unique to this manifest file. The name specified
213here is used as the remote name in each project's .git/config, and is therefore
214automatically available to commands like `git fetch`, `git remote`, `git pull`
215and `git push`.
216.PP
217Attribute `alias`: The alias, if specified, is used to override `name` to be set
218as the remote name in each project's .git/config. Its value can be duplicated
219while attribute `name` has to be unique in the manifest file. This helps each
220project to be able to have same remote name which actually points to different
221remote url.
222.PP
223Attribute `fetch`: The Git URL prefix for all projects which use this remote.
224Each project's name is appended to this prefix to form the actual URL used to
225clone the project.
226.PP
227Attribute `pushurl`: The Git "push" URL prefix for all projects which use this
228remote. Each project's name is appended to this prefix to form the actual URL
229used to "git push" the project. This attribute is optional; if not specified
230then "git push" will use the same URL as the `fetch` attribute.
231.PP
232Attribute `review`: Hostname of the Gerrit server where reviews are uploaded to
233by `repo upload`. This attribute is optional; if not specified then `repo
234upload` will not function.
235.PP
236Attribute `revision`: Name of a Git branch (e.g. `main` or `refs/heads/main`).
237Remotes with their own revision will override the default revision.
238.PP
239Element default
240.PP
241At most one default element may be specified. Its remote and revision attributes
242are used when a project element does not specify its own remote or revision
243attribute.
244.PP
245Attribute `remote`: Name of a previously defined remote element. Project
246elements lacking a remote attribute of their own will use this remote.
247.PP
248Attribute `revision`: Name of a Git branch (e.g. `main` or `refs/heads/main`).
249Project elements lacking their own revision attribute will use this revision.
250.PP
251Attribute `dest\-branch`: Name of a Git branch (e.g. `main`). Project elements
252not setting their own `dest\-branch` will inherit this value. If this value is
253not set, projects will use `revision` by default instead.
254.PP
255Attribute `upstream`: Name of the Git ref in which a sha1 can be found. Used
256when syncing a revision locked manifest in \fB\-c\fR mode to avoid having to sync the
257entire ref space. Project elements not setting their own `upstream` will inherit
258this value.
259.PP
260Attribute `sync\-j`: Number of parallel jobs to use when synching.
261.PP
262Attribute `sync\-c`: Set to true to only sync the given Git branch (specified in
263the `revision` attribute) rather than the whole ref space. Project elements
264lacking a sync\-c element of their own will use this value.
265.PP
266Attribute `sync\-s`: Set to true to also sync sub\-projects.
267.PP
268Attribute `sync\-tags`: Set to false to only sync the given Git branch (specified
269in the `revision` attribute) rather than the other ref tags.
270.PP
271Element manifest\-server
272.PP
273At most one manifest\-server may be specified. The url attribute is used to
274specify the URL of a manifest server, which is an XML RPC service.
275.PP
276The manifest server should implement the following RPC methods:
277.IP
278GetApprovedManifest(branch, target)
279.PP
280Return a manifest in which each project is pegged to a known good revision for
281the current branch and target. This is used by repo sync when the \fB\-\-smart\-sync\fR
282option is given.
283.PP
284The target to use is defined by environment variables TARGET_PRODUCT and
285TARGET_BUILD_VARIANT. These variables are used to create a string of the form
286$TARGET_PRODUCT\-$TARGET_BUILD_VARIANT, e.g. passion\-userdebug. If one of those
287variables or both are not present, the program will call GetApprovedManifest
288without the target parameter and the manifest server should choose a reasonable
289default target.
290.IP
291GetManifest(tag)
292.PP
293Return a manifest in which each project is pegged to the revision at the
294specified tag. This is used by repo sync when the \fB\-\-smart\-tag\fR option is given.
295.PP
296Element project
297.PP
298One or more project elements may be specified. Each element describes a single
299Git repository to be cloned into the repo client workspace. You may specify
300Git\-submodules by creating a nested project. Git\-submodules will be
301automatically recognized and inherit their parent's attributes, but those may be
302overridden by an explicitly specified project element.
303.PP
304Attribute `name`: A unique name for this project. The project's name is appended
305onto its remote's fetch URL to generate the actual URL to configure the Git
306remote with. The URL gets formed as:
307.IP
308${remote_fetch}/${project_name}.git
309.PP
310where ${remote_fetch} is the remote's fetch attribute and ${project_name} is the
311project's name attribute. The suffix ".git" is always appended as repo assumes
312the upstream is a forest of bare Git repositories. If the project has a parent
313element, its name will be prefixed by the parent's.
314.PP
315The project name must match the name Gerrit knows, if Gerrit is being used for
316code reviews.
317.PP
318"name" must not be empty, and may not be an absolute path or use "." or ".."
319path components. It is always interpreted relative to the remote's fetch
320settings, so if a different base path is needed, declare a different remote with
321the new settings needed. These restrictions are not enforced for [Local
322Manifests].
323.PP
324Attribute `path`: An optional path relative to the top directory of the repo
325client where the Git working directory for this project should be placed. If not
326supplied the project "name" is used. If the project has a parent element, its
327path will be prefixed by the parent's.
328.PP
329"path" may not be an absolute path or use "." or ".." path components. These
330restrictions are not enforced for [Local Manifests].
331.PP
332If you want to place files into the root of the checkout (e.g. a README or
333Makefile or another build script), use the [copyfile] or [linkfile] elements
334instead.
335.PP
336Attribute `remote`: Name of a previously defined remote element. If not supplied
337the remote given by the default element is used.
338.PP
339Attribute `revision`: Name of the Git branch the manifest wants to track for
340this project. Names can be relative to refs/heads (e.g. just "main") or absolute
341(e.g. "refs/heads/main"). Tags and/or explicit SHA\-1s should work in theory, but
342have not been extensively tested. If not supplied the revision given by the
343remote element is used if applicable, else the default element is used.
344.PP
345Attribute `dest\-branch`: Name of a Git branch (e.g. `main`). When using `repo
346upload`, changes will be submitted for code review on this branch. If
347unspecified both here and in the default element, `revision` is used instead.
348.PP
349Attribute `groups`: List of groups to which this project belongs, whitespace or
350comma separated. All projects belong to the group "all", and each project
351automatically belongs to a group of its name:`name` and path:`path`. E.g. for
352`<project name="monkeys" path="barrel\-of"/>`, that project definition is
353implicitly in the following manifest groups: default, name:monkeys, and
354path:barrel\-of. If you place a project in the group "notdefault", it will not be
355automatically downloaded by repo. If the project has a parent element, the
356`name` and `path` here are the prefixed ones.
357.PP
358Attribute `sync\-c`: Set to true to only sync the given Git branch (specified in
359the `revision` attribute) rather than the whole ref space.
360.PP
361Attribute `sync\-s`: Set to true to also sync sub\-projects.
362.PP
363Attribute `upstream`: Name of the Git ref in which a sha1 can be found. Used
364when syncing a revision locked manifest in \fB\-c\fR mode to avoid having to sync the
365entire ref space.
366.PP
367Attribute `clone\-depth`: Set the depth to use when fetching this project. If
368specified, this value will override any value given to repo init with the
369\fB\-\-depth\fR option on the command line.
370.PP
371Attribute `force\-path`: Set to true to force this project to create the local
372mirror repository according to its `path` attribute (if supplied) rather than
373the `name` attribute. This attribute only applies to the local mirrors syncing,
374it will be ignored when syncing the projects in a client working directory.
375.PP
376Element extend\-project
377.PP
378Modify the attributes of the named project.
379.PP
380This element is mostly useful in a local manifest file, to modify the attributes
381of an existing project without completely replacing the existing project
382definition. This makes the local manifest more robust against changes to the
383original manifest.
384.PP
385Attribute `path`: If specified, limit the change to projects checked out at the
386specified path, rather than all projects with the given name.
387.PP
388Attribute `groups`: List of additional groups to which this project belongs.
389Same syntax as the corresponding element of `project`.
390.PP
391Attribute `revision`: If specified, overrides the revision of the original
392project. Same syntax as the corresponding element of `project`.
393.PP
394Attribute `remote`: If specified, overrides the remote of the original project.
395Same syntax as the corresponding element of `project`.
396.PP
397Element annotation
398.PP
399Zero or more annotation elements may be specified as children of a project or
400remote element. Each element describes a name\-value pair. For projects, this
401name\-value pair will be exported into each project's environment during a
402\&'forall' command, prefixed with `REPO__`. In addition, there is an optional
403attribute "keep" which accepts the case insensitive values "true" (default) or
404"false". This attribute determines whether or not the annotation will be kept
405when exported with the manifest subcommand.
406.PP
407Element copyfile
408.PP
409Zero or more copyfile elements may be specified as children of a project
410element. Each element describes a src\-dest pair of files; the "src" file will be
411copied to the "dest" place during `repo sync` command.
412.PP
413"src" is project relative, "dest" is relative to the top of the tree. Copying
414from paths outside of the project or to paths outside of the repo client is not
415allowed.
416.PP
417"src" and "dest" must be files. Directories or symlinks are not allowed.
418Intermediate paths must not be symlinks either.
419.PP
420Parent directories of "dest" will be automatically created if missing.
421.PP
422Element linkfile
423.PP
424It's just like copyfile and runs at the same time as copyfile but instead of
425copying it creates a symlink.
426.PP
427The symlink is created at "dest" (relative to the top of the tree) and points to
428the path specified by "src" which is a path in the project.
429.PP
430Parent directories of "dest" will be automatically created if missing.
431.PP
432The symlink target may be a file or directory, but it may not point outside of
433the repo client.
434.PP
435Element remove\-project
436.PP
437Deletes the named project from the internal manifest table, possibly allowing a
438subsequent project element in the same manifest file to replace the project with
439a different source.
440.PP
441This element is mostly useful in a local manifest file, where the user can
442remove a project, and possibly replace it with their own definition.
443.PP
444Attribute `optional`: Set to true to ignore remove\-project elements with no
445matching `project` element.
446.PP
447Element repo\-hooks
448.PP
449NB: See the [practical documentation](./repo\-hooks.md) for using repo hooks.
450.PP
451Only one repo\-hooks element may be specified at a time. Attempting to redefine
452it will fail to parse.
453.PP
454Attribute `in\-project`: The project where the hooks are defined. The value must
455match the `name` attribute (**not** the `path` attribute) of a previously
456defined `project` element.
457.PP
458Attribute `enabled\-list`: List of hooks to use, whitespace or comma separated.
459.PP
460Element superproject
461.PP
462*** *Note*: This is currently a WIP. ***
463.PP
464NB: See the [git superprojects documentation](
465https://en.wikibooks.org/wiki/Git/Submodules_and_Superprojects) for background
466information.
467.PP
468This element is used to specify the URL of the superproject. It has "name" and
469"remote" as atrributes. Only "name" is required while the others have reasonable
470defaults. At most one superproject may be specified. Attempting to redefine it
471will fail to parse.
472.PP
473Attribute `name`: A unique name for the superproject. This attribute has the
474same meaning as project's name attribute. See the [element
475project](#element\-project) for more information.
476.PP
477Attribute `remote`: Name of a previously defined remote element. If not supplied
478the remote given by the default element is used.
479.PP
480Element contactinfo
481.PP
482*** *Note*: This is currently a WIP. ***
483.PP
484This element is used to let manifest authors self\-register contact info. It has
485"bugurl" as a required atrribute. This element can be repeated, and any later
486entries will clobber earlier ones. This would allow manifest authors who extend
487manifests to specify their own contact info.
488.PP
489Attribute `bugurl`: The URL to file a bug against the manifest owner.
490.PP
491Element include
492.PP
493This element provides the capability of including another manifest file into the
494originating manifest. Normal rules apply for the target manifest to include \- it
495must be a usable manifest on its own.
496.PP
497Attribute `name`: the manifest to include, specified relative to the manifest
498repository's root.
499.PP
500"name" may not be an absolute path or use "." or ".." path components. These
501restrictions are not enforced for [Local Manifests].
502.PP
503Attribute `groups`: List of additional groups to which all projects in the
504included manifest belong. This appends and recurses, meaning all projects in
505sub\-manifests carry all parent include groups. Same syntax as the corresponding
506element of `project`.
507.PP
508Local Manifests
509.PP
510Additional remotes and projects may be added through local manifest files stored
511in `$TOP_DIR/.repo/local_manifests/*.xml`.
512.PP
513For example:
514.IP
515\f(CW$ ls .repo/local_manifests\fR
516.IP
517local_manifest.xml
518another_local_manifest.xml
519.IP
520\f(CW$ cat .repo/local_manifests/local_manifest.xml\fR
521.IP
522<?xml version="1.0" encoding="UTF\-8"?>
523<manifest>
524.IP
525<project path="manifest"
526.IP
527name="tools/manifest" />
528.IP
529<project path="platform\-manifest"
530.IP
531name="platform/manifest" />
532.IP
533</manifest>
534.PP
535Users may add projects to the local manifest(s) prior to a `repo sync`
536invocation, instructing repo to automatically download and manage these extra
537projects.
538.PP
539Manifest files stored in `$TOP_DIR/.repo/local_manifests/*.xml` will be loaded
540in alphabetical order.
541.PP
542Projects from local manifest files are added into local::<local manifest
543filename> group.
544.PP
545The legacy `$TOP_DIR/.repo/local_manifest.xml` path is no longer supported.
546.SS [copyfile]: #Element\-copyfile [linkfile]: #Element\-linkfile [Local Manifests]:
547.PP
548#local\-manifests
diff --git a/man/repo-overview.1 b/man/repo-overview.1
new file mode 100644
index 00000000..a12c7640
--- /dev/null
+++ b/man/repo-overview.1
@@ -0,0 +1,39 @@
1.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
2.TH REPO "1" "July 2021" "repo overview" "Repo Manual"
3.SH NAME
4repo \- repo overview - manual page for repo overview
5.SH SYNOPSIS
6.B repo
7\fI\,overview \/\fR[\fI\,--current-branch\/\fR] [\fI\,<project>\/\fR...]
8.SH DESCRIPTION
9Summary
10.PP
11Display overview of unmerged project branches
12.SH OPTIONS
13.TP
14\fB\-h\fR, \fB\-\-help\fR
15show this help message and exit
16.TP
17\fB\-c\fR, \fB\-\-current\-branch\fR
18consider only checked out branches
19.TP
20\fB\-\-no\-current\-branch\fR
21consider all local branches
22.SS Logging options:
23.TP
24\fB\-v\fR, \fB\-\-verbose\fR
25show all output
26.TP
27\fB\-q\fR, \fB\-\-quiet\fR
28only show errors
29.PP
30Run `repo help overview` to view the detailed manual.
31.SH DETAILS
32.PP
33The 'repo overview' command is used to display an overview of the projects
34branches, and list any local commits that have not yet been merged into the
35project.
36.PP
37The \fB\-c\fR/\-\-current\-branch option can be used to restrict the output to only
38branches currently checked out in each project. By default, all branches are
39displayed.
diff --git a/man/repo-prune.1 b/man/repo-prune.1
new file mode 100644
index 00000000..bd68a373
--- /dev/null
+++ b/man/repo-prune.1
@@ -0,0 +1,28 @@
1.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
2.TH REPO "1" "July 2021" "repo prune" "Repo Manual"
3.SH NAME
4repo \- repo prune - manual page for repo prune
5.SH SYNOPSIS
6.B repo
7\fI\,prune \/\fR[\fI\,<project>\/\fR...]
8.SH DESCRIPTION
9Summary
10.PP
11Prune (delete) already merged topics
12.SH OPTIONS
13.TP
14\fB\-h\fR, \fB\-\-help\fR
15show this help message and exit
16.TP
17\fB\-j\fR JOBS, \fB\-\-jobs\fR=\fI\,JOBS\/\fR
18number of jobs to run in parallel (default: based on
19number of CPU cores)
20.SS Logging options:
21.TP
22\fB\-v\fR, \fB\-\-verbose\fR
23show all output
24.TP
25\fB\-q\fR, \fB\-\-quiet\fR
26only show errors
27.PP
28Run `repo help prune` to view the detailed manual.
diff --git a/man/repo-rebase.1 b/man/repo-rebase.1
new file mode 100644
index 00000000..aa261036
--- /dev/null
+++ b/man/repo-rebase.1
@@ -0,0 +1,55 @@
1.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
2.TH REPO "1" "July 2021" "repo rebase" "Repo Manual"
3.SH NAME
4repo \- repo rebase - manual page for repo rebase
5.SH SYNOPSIS
6.B repo
7\fI\,rebase {\/\fR[\fI\,<project>\/\fR...] \fI\,| -i <project>\/\fR...\fI\,}\/\fR
8.SH DESCRIPTION
9Summary
10.PP
11Rebase local branches on upstream branch
12.SH OPTIONS
13.TP
14\fB\-h\fR, \fB\-\-help\fR
15show this help message and exit
16.TP
17\fB\-\-fail\-fast\fR
18stop rebasing after first error is hit
19.TP
20\fB\-f\fR, \fB\-\-force\-rebase\fR
21pass \fB\-\-force\-rebase\fR to git rebase
22.TP
23\fB\-\-no\-ff\fR
24pass \fB\-\-no\-ff\fR to git rebase
25.TP
26\fB\-\-autosquash\fR
27pass \fB\-\-autosquash\fR to git rebase
28.TP
29\fB\-\-whitespace\fR=\fI\,WS\/\fR
30pass \fB\-\-whitespace\fR to git rebase
31.TP
32\fB\-\-auto\-stash\fR
33stash local modifications before starting
34.TP
35\fB\-m\fR, \fB\-\-onto\-manifest\fR
36rebase onto the manifest version instead of upstream
37HEAD (this helps to make sure the local tree stays
38consistent if you previously synced to a manifest)
39.SS Logging options:
40.TP
41\fB\-v\fR, \fB\-\-verbose\fR
42show all output
43.TP
44\fB\-q\fR, \fB\-\-quiet\fR
45only show errors
46.TP
47\fB\-i\fR, \fB\-\-interactive\fR
48interactive rebase (single project only)
49.PP
50Run `repo help rebase` to view the detailed manual.
51.SH DETAILS
52.PP
53\&'repo rebase' uses git rebase to move local changes in the current topic branch
54to the HEAD of the upstream history, useful when you have made commits in a
55topic branch but need to incorporate new upstream changes "underneath" them.
diff --git a/man/repo-selfupdate.1 b/man/repo-selfupdate.1
new file mode 100644
index 00000000..70c855ab
--- /dev/null
+++ b/man/repo-selfupdate.1
@@ -0,0 +1,35 @@
1.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
2.TH REPO "1" "July 2021" "repo selfupdate" "Repo Manual"
3.SH NAME
4repo \- repo selfupdate - manual page for repo selfupdate
5.SH SYNOPSIS
6.B repo
7\fI\,selfupdate\/\fR
8.SH DESCRIPTION
9Summary
10.PP
11Update repo to the latest version
12.SH OPTIONS
13.TP
14\fB\-h\fR, \fB\-\-help\fR
15show this help message and exit
16.SS Logging options:
17.TP
18\fB\-v\fR, \fB\-\-verbose\fR
19show all output
20.TP
21\fB\-q\fR, \fB\-\-quiet\fR
22only show errors
23.SS repo Version options:
24.TP
25\fB\-\-no\-repo\-verify\fR
26do not verify repo source code
27.PP
28Run `repo help selfupdate` to view the detailed manual.
29.SH DETAILS
30.PP
31The 'repo selfupdate' command upgrades repo to the latest version, if a newer
32version is available.
33.PP
34Normally this is done automatically by 'repo sync' and does not need to be
35performed by an end\-user.
diff --git a/man/repo-smartsync.1 b/man/repo-smartsync.1
new file mode 100644
index 00000000..5d939117
--- /dev/null
+++ b/man/repo-smartsync.1
@@ -0,0 +1,118 @@
1.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
2.TH REPO "1" "July 2021" "repo smartsync" "Repo Manual"
3.SH NAME
4repo \- repo smartsync - manual page for repo smartsync
5.SH SYNOPSIS
6.B repo
7\fI\,smartsync \/\fR[\fI\,<project>\/\fR...]
8.SH DESCRIPTION
9Summary
10.PP
11Update working tree to the latest known good revision
12.SH OPTIONS
13.TP
14\fB\-h\fR, \fB\-\-help\fR
15show this help message and exit
16.TP
17\fB\-j\fR JOBS, \fB\-\-jobs\fR=\fI\,JOBS\/\fR
18number of jobs to run in parallel (default: based on
19number of CPU cores)
20.TP
21\fB\-\-jobs\-network\fR=\fI\,JOBS\/\fR
22number of network jobs to run in parallel (defaults to
23\fB\-\-jobs\fR)
24.TP
25\fB\-\-jobs\-checkout\fR=\fI\,JOBS\/\fR
26number of local checkout jobs to run in parallel
27(defaults to \fB\-\-jobs\fR)
28.TP
29\fB\-f\fR, \fB\-\-force\-broken\fR
30obsolete option (to be deleted in the future)
31.TP
32\fB\-\-fail\-fast\fR
33stop syncing after first error is hit
34.TP
35\fB\-\-force\-sync\fR
36overwrite an existing git directory if it needs to
37point to a different object directory. WARNING: this
38may cause loss of data
39.TP
40\fB\-\-force\-remove\-dirty\fR
41force remove projects with uncommitted modifications
42if projects no longer exist in the manifest. WARNING:
43this may cause loss of data
44.TP
45\fB\-l\fR, \fB\-\-local\-only\fR
46only update working tree, don't fetch
47.TP
48\fB\-\-no\-manifest\-update\fR, \fB\-\-nmu\fR
49use the existing manifest checkout as\-is. (do not
50update to the latest revision)
51.TP
52\fB\-n\fR, \fB\-\-network\-only\fR
53fetch only, don't update working tree
54.TP
55\fB\-d\fR, \fB\-\-detach\fR
56detach projects back to manifest revision
57.TP
58\fB\-c\fR, \fB\-\-current\-branch\fR
59fetch only current branch from server
60.TP
61\fB\-\-no\-current\-branch\fR
62fetch all branches from server
63.TP
64\fB\-m\fR NAME.xml, \fB\-\-manifest\-name\fR=\fI\,NAME\/\fR.xml
65temporary manifest to use for this sync
66.TP
67\fB\-\-clone\-bundle\fR
68enable use of \fI\,/clone.bundle\/\fP on HTTP/HTTPS
69.TP
70\fB\-\-no\-clone\-bundle\fR
71disable use of \fI\,/clone.bundle\/\fP on HTTP/HTTPS
72.TP
73\fB\-u\fR MANIFEST_SERVER_USERNAME, \fB\-\-manifest\-server\-username\fR=\fI\,MANIFEST_SERVER_USERNAME\/\fR
74username to authenticate with the manifest server
75.TP
76\fB\-p\fR MANIFEST_SERVER_PASSWORD, \fB\-\-manifest\-server\-password\fR=\fI\,MANIFEST_SERVER_PASSWORD\/\fR
77password to authenticate with the manifest server
78.TP
79\fB\-\-fetch\-submodules\fR
80fetch submodules from server
81.TP
82\fB\-\-use\-superproject\fR
83use the manifest superproject to sync projects
84.TP
85\fB\-\-no\-use\-superproject\fR
86disable use of manifest superprojects
87.TP
88\fB\-\-tags\fR
89fetch tags
90.TP
91\fB\-\-no\-tags\fR
92don't fetch tags
93.TP
94\fB\-\-optimized\-fetch\fR
95only fetch projects fixed to sha1 if revision does not
96exist locally
97.TP
98\fB\-\-retry\-fetches\fR=\fI\,RETRY_FETCHES\/\fR
99number of times to retry fetches on transient errors
100.TP
101\fB\-\-prune\fR
102delete refs that no longer exist on the remote
103.SS Logging options:
104.TP
105\fB\-v\fR, \fB\-\-verbose\fR
106show all output
107.TP
108\fB\-q\fR, \fB\-\-quiet\fR
109only show errors
110.SS repo Version options:
111.TP
112\fB\-\-no\-repo\-verify\fR
113do not verify repo source code
114.PP
115Run `repo help smartsync` to view the detailed manual.
116.SH DETAILS
117.PP
118The 'repo smartsync' command is a shortcut for sync \fB\-s\fR.
diff --git a/man/repo-stage.1 b/man/repo-stage.1
new file mode 100644
index 00000000..07e1cac6
--- /dev/null
+++ b/man/repo-stage.1
@@ -0,0 +1,30 @@
1.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
2.TH REPO "1" "July 2021" "repo stage" "Repo Manual"
3.SH NAME
4repo \- repo stage - manual page for repo stage
5.SH SYNOPSIS
6.B repo
7\fI\,stage -i \/\fR[\fI\,<project>\/\fR...]
8.SH DESCRIPTION
9Summary
10.PP
11Stage file(s) for commit
12.SH OPTIONS
13.TP
14\fB\-h\fR, \fB\-\-help\fR
15show this help message and exit
16.SS Logging options:
17.TP
18\fB\-v\fR, \fB\-\-verbose\fR
19show all output
20.TP
21\fB\-q\fR, \fB\-\-quiet\fR
22only show errors
23.TP
24\fB\-i\fR, \fB\-\-interactive\fR
25use interactive staging
26.PP
27Run `repo help stage` to view the detailed manual.
28.SH DETAILS
29.PP
30The 'repo stage' command stages files to prepare the next commit.
diff --git a/man/repo-start.1 b/man/repo-start.1
new file mode 100644
index 00000000..b00a31f4
--- /dev/null
+++ b/man/repo-start.1
@@ -0,0 +1,41 @@
1.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
2.TH REPO "1" "July 2021" "repo start" "Repo Manual"
3.SH NAME
4repo \- repo start - manual page for repo start
5.SH SYNOPSIS
6.B repo
7\fI\,start <newbranchname> \/\fR[\fI\,--all | <project>\/\fR...]
8.SH DESCRIPTION
9Summary
10.PP
11Start a new branch for development
12.SH OPTIONS
13.TP
14\fB\-h\fR, \fB\-\-help\fR
15show this help message and exit
16.TP
17\fB\-j\fR JOBS, \fB\-\-jobs\fR=\fI\,JOBS\/\fR
18number of jobs to run in parallel (default: based on
19number of CPU cores)
20.TP
21\fB\-\-all\fR
22begin branch in all projects
23.TP
24\fB\-r\fR REVISION, \fB\-\-rev\fR=\fI\,REVISION\/\fR, \fB\-\-revision\fR=\fI\,REVISION\/\fR
25point branch at this revision instead of upstream
26.TP
27\fB\-\-head\fR, \fB\-\-HEAD\fR
28abbreviation for \fB\-\-rev\fR HEAD
29.SS Logging options:
30.TP
31\fB\-v\fR, \fB\-\-verbose\fR
32show all output
33.TP
34\fB\-q\fR, \fB\-\-quiet\fR
35only show errors
36.PP
37Run `repo help start` to view the detailed manual.
38.SH DETAILS
39.PP
40\&'repo start' begins a new branch of development, starting from the revision
41specified in the manifest.
diff --git a/man/repo-status.1 b/man/repo-status.1
new file mode 100644
index 00000000..fbae2c5d
--- /dev/null
+++ b/man/repo-status.1
@@ -0,0 +1,98 @@
1.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
2.TH REPO "1" "July 2021" "repo status" "Repo Manual"
3.SH NAME
4repo \- repo status - manual page for repo status
5.SH SYNOPSIS
6.B repo
7\fI\,status \/\fR[\fI\,<project>\/\fR...]
8.SH DESCRIPTION
9Summary
10.PP
11Show the working tree status
12.SH OPTIONS
13.TP
14\fB\-h\fR, \fB\-\-help\fR
15show this help message and exit
16.TP
17\fB\-j\fR JOBS, \fB\-\-jobs\fR=\fI\,JOBS\/\fR
18number of jobs to run in parallel (default: based on
19number of CPU cores)
20.TP
21\fB\-o\fR, \fB\-\-orphans\fR
22include objects in working directory outside of repo
23projects
24.SS Logging options:
25.TP
26\fB\-v\fR, \fB\-\-verbose\fR
27show all output
28.TP
29\fB\-q\fR, \fB\-\-quiet\fR
30only show errors
31.PP
32Run `repo help status` to view the detailed manual.
33.SH DETAILS
34.PP
35\&'repo status' compares the working tree to the staging area (aka index), and the
36most recent commit on this branch (HEAD), in each project specified. A summary
37is displayed, one line per file where there is a difference between these three
38states.
39.PP
40The \fB\-j\fR/\-\-jobs option can be used to run multiple status queries in parallel.
41.PP
42The \fB\-o\fR/\-\-orphans option can be used to show objects that are in the working
43directory, but not associated with a repo project. This includes unmanaged
44top\-level files and directories, but also includes deeper items. For example, if
45dir/subdir/proj1 and dir/subdir/proj2 are repo projects, dir/subdir/proj3 will
46be shown if it is not known to repo.
47.PP
48Status Display
49.PP
50The status display is organized into three columns of information, for example
51if the file 'subcmds/status.py' is modified in the project 'repo' on branch
52\&'devwork':
53.TP
54project repo/
55branch devwork
56.TP
57\fB\-m\fR
58subcmds/status.py
59.PP
60The first column explains how the staging area (index) differs from the last
61commit (HEAD). Its values are always displayed in upper case and have the
62following meanings:
63.TP
64\-:
65no difference
66.TP
67A:
68added (not in HEAD, in index )
69.TP
70M:
71modified ( in HEAD, in index, different content )
72.TP
73D:
74deleted ( in HEAD, not in index )
75.TP
76R:
77renamed (not in HEAD, in index, path changed )
78.TP
79C:
80copied (not in HEAD, in index, copied from another)
81.TP
82T:
83mode changed ( in HEAD, in index, same content )
84.TP
85U:
86unmerged; conflict resolution required
87.PP
88The second column explains how the working directory differs from the index. Its
89values are always displayed in lower case and have the following meanings:
90.TP
91\-:
92new / unknown (not in index, in work tree )
93.TP
94m:
95modified ( in index, in work tree, modified )
96.TP
97d:
98deleted ( in index, not in work tree )
diff --git a/man/repo-sync.1 b/man/repo-sync.1
new file mode 100644
index 00000000..c87c9701
--- /dev/null
+++ b/man/repo-sync.1
@@ -0,0 +1,209 @@
1.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
2.TH REPO "1" "July 2021" "repo sync" "Repo Manual"
3.SH NAME
4repo \- repo sync - manual page for repo sync
5.SH SYNOPSIS
6.B repo
7\fI\,sync \/\fR[\fI\,<project>\/\fR...]
8.SH DESCRIPTION
9Summary
10.PP
11Update working tree to the latest revision
12.SH OPTIONS
13.TP
14\fB\-h\fR, \fB\-\-help\fR
15show this help message and exit
16.TP
17\fB\-j\fR JOBS, \fB\-\-jobs\fR=\fI\,JOBS\/\fR
18number of jobs to run in parallel (default: based on
19number of CPU cores)
20.TP
21\fB\-\-jobs\-network\fR=\fI\,JOBS\/\fR
22number of network jobs to run in parallel (defaults to
23\fB\-\-jobs\fR)
24.TP
25\fB\-\-jobs\-checkout\fR=\fI\,JOBS\/\fR
26number of local checkout jobs to run in parallel
27(defaults to \fB\-\-jobs\fR)
28.TP
29\fB\-f\fR, \fB\-\-force\-broken\fR
30obsolete option (to be deleted in the future)
31.TP
32\fB\-\-fail\-fast\fR
33stop syncing after first error is hit
34.TP
35\fB\-\-force\-sync\fR
36overwrite an existing git directory if it needs to
37point to a different object directory. WARNING: this
38may cause loss of data
39.TP
40\fB\-\-force\-remove\-dirty\fR
41force remove projects with uncommitted modifications
42if projects no longer exist in the manifest. WARNING:
43this may cause loss of data
44.TP
45\fB\-l\fR, \fB\-\-local\-only\fR
46only update working tree, don't fetch
47.TP
48\fB\-\-no\-manifest\-update\fR, \fB\-\-nmu\fR
49use the existing manifest checkout as\-is. (do not
50update to the latest revision)
51.TP
52\fB\-n\fR, \fB\-\-network\-only\fR
53fetch only, don't update working tree
54.TP
55\fB\-d\fR, \fB\-\-detach\fR
56detach projects back to manifest revision
57.TP
58\fB\-c\fR, \fB\-\-current\-branch\fR
59fetch only current branch from server
60.TP
61\fB\-\-no\-current\-branch\fR
62fetch all branches from server
63.TP
64\fB\-m\fR NAME.xml, \fB\-\-manifest\-name\fR=\fI\,NAME\/\fR.xml
65temporary manifest to use for this sync
66.TP
67\fB\-\-clone\-bundle\fR
68enable use of \fI\,/clone.bundle\/\fP on HTTP/HTTPS
69.TP
70\fB\-\-no\-clone\-bundle\fR
71disable use of \fI\,/clone.bundle\/\fP on HTTP/HTTPS
72.TP
73\fB\-u\fR MANIFEST_SERVER_USERNAME, \fB\-\-manifest\-server\-username\fR=\fI\,MANIFEST_SERVER_USERNAME\/\fR
74username to authenticate with the manifest server
75.TP
76\fB\-p\fR MANIFEST_SERVER_PASSWORD, \fB\-\-manifest\-server\-password\fR=\fI\,MANIFEST_SERVER_PASSWORD\/\fR
77password to authenticate with the manifest server
78.TP
79\fB\-\-fetch\-submodules\fR
80fetch submodules from server
81.TP
82\fB\-\-use\-superproject\fR
83use the manifest superproject to sync projects
84.TP
85\fB\-\-no\-use\-superproject\fR
86disable use of manifest superprojects
87.TP
88\fB\-\-tags\fR
89fetch tags
90.TP
91\fB\-\-no\-tags\fR
92don't fetch tags
93.TP
94\fB\-\-optimized\-fetch\fR
95only fetch projects fixed to sha1 if revision does not
96exist locally
97.TP
98\fB\-\-retry\-fetches\fR=\fI\,RETRY_FETCHES\/\fR
99number of times to retry fetches on transient errors
100.TP
101\fB\-\-prune\fR
102delete refs that no longer exist on the remote
103.TP
104\fB\-s\fR, \fB\-\-smart\-sync\fR
105smart sync using manifest from the latest known good
106build
107.TP
108\fB\-t\fR SMART_TAG, \fB\-\-smart\-tag\fR=\fI\,SMART_TAG\/\fR
109smart sync using manifest from a known tag
110.SS Logging options:
111.TP
112\fB\-v\fR, \fB\-\-verbose\fR
113show all output
114.TP
115\fB\-q\fR, \fB\-\-quiet\fR
116only show errors
117.SS repo Version options:
118.TP
119\fB\-\-no\-repo\-verify\fR
120do not verify repo source code
121.PP
122Run `repo help sync` to view the detailed manual.
123.SH DETAILS
124.PP
125The 'repo sync' command synchronizes local project directories with the remote
126repositories specified in the manifest. If a local project does not yet exist,
127it will clone a new local directory from the remote repository and set up
128tracking branches as specified in the manifest. If the local project already
129exists, 'repo sync' will update the remote branches and rebase any new local
130changes on top of the new remote changes.
131.PP
132\&'repo sync' will synchronize all projects listed at the command line. Projects
133can be specified either by name, or by a relative or absolute path to the
134project's local directory. If no projects are specified, 'repo sync' will
135synchronize all projects listed in the manifest.
136.PP
137The \fB\-d\fR/\-\-detach option can be used to switch specified projects back to the
138manifest revision. This option is especially helpful if the project is currently
139on a topic branch, but the manifest revision is temporarily needed.
140.PP
141The \fB\-s\fR/\-\-smart\-sync option can be used to sync to a known good build as
142specified by the manifest\-server element in the current manifest. The
143\fB\-t\fR/\-\-smart\-tag option is similar and allows you to specify a custom tag/label.
144.PP
145The \fB\-u\fR/\-\-manifest\-server\-username and \fB\-p\fR/\-\-manifest\-server\-password options can
146be used to specify a username and password to authenticate with the manifest
147server when using the \fB\-s\fR or \fB\-t\fR option.
148.PP
149If \fB\-u\fR and \fB\-p\fR are not specified when using the \fB\-s\fR or \fB\-t\fR option, 'repo sync' will
150attempt to read authentication credentials for the manifest server from the
151user's .netrc file.
152.PP
153\&'repo sync' will not use authentication credentials from \fB\-u\fR/\-p or .netrc if the
154manifest server specified in the manifest file already includes credentials.
155.PP
156By default, all projects will be synced. The \fB\-\-fail\-fast\fR option can be used to
157halt syncing as soon as possible when the first project fails to sync.
158.PP
159The \fB\-\-force\-sync\fR option can be used to overwrite existing git directories if
160they have previously been linked to a different object directory. WARNING: This
161may cause data to be lost since refs may be removed when overwriting.
162.PP
163The \fB\-\-force\-remove\-dirty\fR option can be used to remove previously used projects
164with uncommitted changes. WARNING: This may cause data to be lost since
165uncommitted changes may be removed with projects that no longer exist in the
166manifest.
167.PP
168The \fB\-\-no\-clone\-bundle\fR option disables any attempt to use \fI\,$URL/clone.bundle\/\fP to
169bootstrap a new Git repository from a resumeable bundle file on a content
170delivery network. This may be necessary if there are problems with the local
171Python HTTP client or proxy configuration, but the Git binary works.
172.PP
173The \fB\-\-fetch\-submodules\fR option enables fetching Git submodules of a project from
174server.
175.PP
176The \fB\-c\fR/\-\-current\-branch option can be used to only fetch objects that are on the
177branch specified by a project's revision.
178.PP
179The \fB\-\-optimized\-fetch\fR option can be used to only fetch projects that are fixed
180to a sha1 revision if the sha1 revision does not already exist locally.
181.PP
182The \fB\-\-prune\fR option can be used to remove any refs that no longer exist on the
183remote.
184.PP
185SSH Connections
186.PP
187If at least one project remote URL uses an SSH connection (ssh://, git+ssh://,
188or user@host:path syntax) repo will automatically enable the SSH ControlMaster
189option when connecting to that host. This feature permits other projects in the
190same 'repo sync' session to reuse the same SSH tunnel, saving connection setup
191overheads.
192.PP
193To disable this behavior on UNIX platforms, set the GIT_SSH environment variable
194to 'ssh'. For example:
195.IP
196export GIT_SSH=ssh
197repo sync
198.PP
199Compatibility
200.PP
201This feature is automatically disabled on Windows, due to the lack of UNIX
202domain socket support.
203.PP
204This feature is not compatible with url.insteadof rewrites in the user's
205~/.gitconfig. 'repo sync' is currently not able to perform the rewrite early
206enough to establish the ControlMaster tunnel.
207.PP
208If the remote SSH daemon is Gerrit Code Review, version 2.0.10 or later is
209required to fix a server side protocol bug.
diff --git a/man/repo-upload.1 b/man/repo-upload.1
new file mode 100644
index 00000000..36a0daca
--- /dev/null
+++ b/man/repo-upload.1
@@ -0,0 +1,175 @@
1.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
2.TH REPO "1" "July 2021" "repo upload" "Repo Manual"
3.SH NAME
4repo \- repo upload - manual page for repo upload
5.SH SYNOPSIS
6.B repo
7\fI\,upload \/\fR[\fI\,--re --cc\/\fR] [\fI\,<project>\/\fR]...
8.SH DESCRIPTION
9Summary
10.PP
11Upload changes for code review
12.SH OPTIONS
13.TP
14\fB\-h\fR, \fB\-\-help\fR
15show this help message and exit
16.TP
17\fB\-j\fR JOBS, \fB\-\-jobs\fR=\fI\,JOBS\/\fR
18number of jobs to run in parallel (default: based on
19number of CPU cores)
20.TP
21\fB\-t\fR
22send local branch name to Gerrit Code Review
23.TP
24\fB\-\-hashtag\fR=\fI\,HASHTAGS\/\fR, \fB\-\-ht\fR=\fI\,HASHTAGS\/\fR
25add hashtags (comma delimited) to the review
26.TP
27\fB\-\-hashtag\-branch\fR, \fB\-\-htb\fR
28add local branch name as a hashtag
29.TP
30\fB\-l\fR LABELS, \fB\-\-label\fR=\fI\,LABELS\/\fR
31add a label when uploading
32.TP
33\fB\-\-re\fR=\fI\,REVIEWERS\/\fR, \fB\-\-reviewers\fR=\fI\,REVIEWERS\/\fR
34request reviews from these people
35.TP
36\fB\-\-cc\fR=\fI\,CC\/\fR
37also send email to these email addresses
38.TP
39\fB\-\-br\fR=\fI\,BRANCH\/\fR, \fB\-\-branch\fR=\fI\,BRANCH\/\fR
40(local) branch to upload
41.TP
42\fB\-c\fR, \fB\-\-current\-branch\fR
43upload current git branch
44.TP
45\fB\-\-no\-current\-branch\fR
46upload all git branches
47.TP
48\fB\-\-ne\fR, \fB\-\-no\-emails\fR
49do not send e\-mails on upload
50.TP
51\fB\-p\fR, \fB\-\-private\fR
52upload as a private change (deprecated; use \fB\-\-wip\fR)
53.TP
54\fB\-w\fR, \fB\-\-wip\fR
55upload as a work\-in\-progress change
56.TP
57\fB\-o\fR PUSH_OPTIONS, \fB\-\-push\-option\fR=\fI\,PUSH_OPTIONS\/\fR
58additional push options to transmit
59.TP
60\fB\-D\fR BRANCH, \fB\-\-destination\fR=\fI\,BRANCH\/\fR, \fB\-\-dest\fR=\fI\,BRANCH\/\fR
61submit for review on this target branch
62.TP
63\fB\-n\fR, \fB\-\-dry\-run\fR
64do everything except actually upload the CL
65.TP
66\fB\-y\fR, \fB\-\-yes\fR
67answer yes to all safe prompts
68.TP
69\fB\-\-no\-cert\-checks\fR
70disable verifying ssl certs (unsafe)
71.SS Logging options:
72.TP
73\fB\-v\fR, \fB\-\-verbose\fR
74show all output
75.TP
76\fB\-q\fR, \fB\-\-quiet\fR
77only show errors
78.SS pre\-upload hooks:
79.TP
80\fB\-\-no\-verify\fR
81Do not run the pre\-upload hook.
82.TP
83\fB\-\-verify\fR
84Run the pre\-upload hook without prompting.
85.TP
86\fB\-\-ignore\-hooks\fR
87Do not abort if pre\-upload hooks fail.
88.PP
89Run `repo help upload` to view the detailed manual.
90.SH DETAILS
91.PP
92The 'repo upload' command is used to send changes to the Gerrit Code Review
93system. It searches for topic branches in local projects that have not yet been
94published for review. If multiple topic branches are found, 'repo upload' opens
95an editor to allow the user to select which branches to upload.
96.PP
97\&'repo upload' searches for uploadable changes in all projects listed at the
98command line. Projects can be specified either by name, or by a relative or
99absolute path to the project's local directory. If no projects are specified,
100\&'repo upload' will search for uploadable changes in all projects listed in the
101manifest.
102.PP
103If the \fB\-\-reviewers\fR or \fB\-\-cc\fR options are passed, those emails are added to the
104respective list of users, and emails are sent to any new users. Users passed as
105\fB\-\-reviewers\fR must already be registered with the code review system, or the
106upload will fail.
107.PP
108Configuration
109.PP
110review.URL.autoupload:
111.PP
112To disable the "Upload ... (y/N)?" prompt, you can set a per\-project or global
113Git configuration option. If review.URL.autoupload is set to "true" then repo
114will assume you always answer "y" at the prompt, and will not prompt you
115further. If it is set to "false" then repo will assume you always answer "n",
116and will abort.
117.PP
118review.URL.autoreviewer:
119.PP
120To automatically append a user or mailing list to reviews, you can set a
121per\-project or global Git option to do so.
122.PP
123review.URL.autocopy:
124.PP
125To automatically copy a user or mailing list to all uploaded reviews, you can
126set a per\-project or global Git option to do so. Specifically,
127review.URL.autocopy can be set to a comma separated list of reviewers who you
128always want copied on all uploads with a non\-empty \fB\-\-re\fR argument.
129.PP
130review.URL.username:
131.PP
132Override the username used to connect to Gerrit Code Review. By default the
133local part of the email address is used.
134.PP
135The URL must match the review URL listed in the manifest XML file, or in the
136\&.git/config within the project. For example:
137.IP
138[remote "origin"]
139.IP
140url = git://git.example.com/project.git
141review = http://review.example.com/
142.IP
143[review "http://review.example.com/"]
144.IP
145autoupload = true
146autocopy = johndoe@company.com,my\-team\-alias@company.com
147.PP
148review.URL.uploadtopic:
149.PP
150To add a topic branch whenever uploading a commit, you can set a per\-project or
151global Git option to do so. If review.URL.uploadtopic is set to "true" then repo
152will assume you always want the equivalent of the \fB\-t\fR option to the repo command.
153If unset or set to "false" then repo will make use of only the command line
154option.
155.PP
156review.URL.uploadhashtags:
157.PP
158To add hashtags whenever uploading a commit, you can set a per\-project or global
159Git option to do so. The value of review.URL.uploadhashtags will be used as
160comma delimited hashtags like the \fB\-\-hashtag\fR option.
161.PP
162review.URL.uploadlabels:
163.PP
164To add labels whenever uploading a commit, you can set a per\-project or global
165Git option to do so. The value of review.URL.uploadlabels will be used as comma
166delimited labels like the \fB\-\-label\fR option.
167.PP
168review.URL.uploadnotify:
169.PP
170Control e\-mail notifications when uploading.
171https://gerrit\-review.googlesource.com/Documentation/user\-upload.html#notify
172.PP
173References
174.PP
175Gerrit Code Review: https://www.gerritcodereview.com/
diff --git a/man/repo-version.1 b/man/repo-version.1
new file mode 100644
index 00000000..cc703f61
--- /dev/null
+++ b/man/repo-version.1
@@ -0,0 +1,24 @@
1.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
2.TH REPO "1" "July 2021" "repo version" "Repo Manual"
3.SH NAME
4repo \- repo version - manual page for repo version
5.SH SYNOPSIS
6.B repo
7\fI\,version\/\fR
8.SH DESCRIPTION
9Summary
10.PP
11Display the version of repo
12.SH OPTIONS
13.TP
14\fB\-h\fR, \fB\-\-help\fR
15show this help message and exit
16.SS Logging options:
17.TP
18\fB\-v\fR, \fB\-\-verbose\fR
19show all output
20.TP
21\fB\-q\fR, \fB\-\-quiet\fR
22only show errors
23.PP
24Run `repo help version` to view the detailed manual.
diff --git a/man/repo.1 b/man/repo.1
new file mode 100644
index 00000000..4aa76380
--- /dev/null
+++ b/man/repo.1
@@ -0,0 +1,133 @@
1.\" DO NOT MODIFY THIS FILE! It was generated by help2man.
2.TH REPO "1" "July 2021" "repo" "Repo Manual"
3.SH NAME
4repo \- repository management tool built on top of git
5.SH SYNOPSIS
6.B repo
7[\fI\,-p|--paginate|--no-pager\/\fR] \fI\,COMMAND \/\fR[\fI\,ARGS\/\fR]
8.SH OPTIONS
9.TP
10\fB\-h\fR, \fB\-\-help\fR
11show this help message and exit
12.TP
13\fB\-\-help\-all\fR
14show this help message with all subcommands and exit
15.TP
16\fB\-p\fR, \fB\-\-paginate\fR
17display command output in the pager
18.TP
19\fB\-\-no\-pager\fR
20disable the pager
21.TP
22\fB\-\-color\fR=\fI\,COLOR\/\fR
23control color usage: auto, always, never
24.TP
25\fB\-\-trace\fR
26trace git command execution (REPO_TRACE=1)
27.TP
28\fB\-\-trace\-python\fR
29trace python command execution
30.TP
31\fB\-\-time\fR
32time repo command execution
33.TP
34\fB\-\-version\fR
35display this version of repo
36.TP
37\fB\-\-show\-toplevel\fR
38display the path of the top\-level directory of the
39repo client checkout
40.TP
41\fB\-\-event\-log\fR=\fI\,EVENT_LOG\/\fR
42filename of event log to append timeline to
43.TP
44\fB\-\-git\-trace2\-event\-log\fR=\fI\,GIT_TRACE2_EVENT_LOG\/\fR
45directory to write git trace2 event log to
46.SS "The complete list of recognized repo commands are:"
47.TP
48abandon
49Permanently abandon a development branch
50.TP
51branch
52View current topic branches
53.TP
54branches
55View current topic branches
56.TP
57checkout
58Checkout a branch for development
59.TP
60cherry\-pick
61Cherry\-pick a change.
62.TP
63diff
64Show changes between commit and working tree
65.TP
66diffmanifests
67Manifest diff utility
68.TP
69download
70Download and checkout a change
71.TP
72forall
73Run a shell command in each project
74.TP
75gitc\-delete
76Delete a GITC Client.
77.TP
78gitc\-init
79Initialize a GITC Client.
80.TP
81grep
82Print lines matching a pattern
83.TP
84help
85Display detailed help on a command
86.TP
87info
88Get info on the manifest branch, current branch or unmerged branches
89.TP
90init
91Initialize a repo client checkout in the current directory
92.TP
93list
94List projects and their associated directories
95.TP
96manifest
97Manifest inspection utility
98.TP
99overview
100Display overview of unmerged project branches
101.TP
102prune
103Prune (delete) already merged topics
104.TP
105rebase
106Rebase local branches on upstream branch
107.TP
108selfupdate
109Update repo to the latest version
110.TP
111smartsync
112Update working tree to the latest known good revision
113.TP
114stage
115Stage file(s) for commit
116.TP
117start
118Start a new branch for development
119.TP
120status
121Show the working tree status
122.TP
123sync
124Update working tree to the latest revision
125.TP
126upload
127Upload changes for code review
128.TP
129version
130Display the version of repo
131.PP
132See 'repo help <command>' for more information on a specific command.
133Bug reports: https://bugs.chromium.org/p/gerrit/issues/entry?template=Repo+tool+issue
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-05-15 14:02:20 +0000