.\" DO NOT MODIFY THIS FILE! It was generated by help2man. .TH REPO "1" "November 2021" "repo gitc-init" "Repo Manual" .SH NAME repo \- repo gitc-init - manual page for repo gitc-init .SH SYNOPSIS .B repo \fI\,gitc-init \/\fR[\fI\,options\/\fR] [\fI\,client name\/\fR] .SH DESCRIPTION Summary .PP Initialize a GITC Client. .SH OPTIONS .TP \fB\-h\fR, \fB\-\-help\fR show this help message and exit .SS Logging options: .TP \fB\-v\fR, \fB\-\-verbose\fR show all output .TP \fB\-q\fR, \fB\-\-quiet\fR only show errors .SS Manifest options: .TP \fB\-u\fR URL, \fB\-\-manifest\-url\fR=\fI\,URL\/\fR manifest repository location .TP \fB\-b\fR REVISION, \fB\-\-manifest\-branch\fR=\fI\,REVISION\/\fR manifest branch or revision (use HEAD for default) .TP \fB\-m\fR NAME.xml, \fB\-\-manifest\-name\fR=\fI\,NAME\/\fR.xml initial manifest file .TP \fB\-g\fR GROUP, \fB\-\-groups\fR=\fI\,GROUP\/\fR restrict manifest projects to ones with specified group(s) [default|all|G1,G2,G3|G4,\-G5,\-G6] .TP \fB\-p\fR PLATFORM, \fB\-\-platform\fR=\fI\,PLATFORM\/\fR restrict manifest projects to ones with a specified platform group [auto|all|none|linux|darwin|...] .TP \fB\-\-submodules\fR sync any submodules associated with the manifest repo .TP \fB\-\-standalone\-manifest\fR download the manifest as a static file rather then create a git checkout of the manifest repo .SS Manifest (only) checkout options: .TP \fB\-\-current\-branch\fR fetch only current manifest branch from server .TP \fB\-\-no\-current\-branch\fR fetch all manifest branches from server .TP \fB\-\-tags\fR fetch tags in the manifest .TP \fB\-\-no\-tags\fR don't fetch tags in the manifest .SS Checkout modes: .TP \fB\-\-mirror\fR create a replica of the remote repositories rather than a client working directory .TP \fB\-\-archive\fR checkout an archive instead of a git repository for each project. See git archive. .TP \fB\-\-worktree\fR use git\-worktree to manage projects .SS Project checkout optimizations: .TP \fB\-\-reference\fR=\fI\,DIR\/\fR location of mirror directory .TP \fB\-\-dissociate\fR dissociate from reference mirrors after clone .TP \fB\-\-depth\fR=\fI\,DEPTH\/\fR create a shallow clone with given depth; see git clone .TP \fB\-\-partial\-clone\fR perform partial clone (https://gitscm.com/docs/gitrepositorylayout#_code_partialclone_code) .TP \fB\-\-no\-partial\-clone\fR disable use of partial clone (https://gitscm.com/docs/gitrepositorylayout#_code_partialclone_code) .TP \fB\-\-partial\-clone\-exclude\fR=\fI\,PARTIAL_CLONE_EXCLUDE\/\fR exclude the specified projects (a comma\-delimited project names) from partial clone (https://gitscm.com/docs/gitrepositorylayout#_code_partialclone_code) .TP \fB\-\-clone\-filter\fR=\fI\,CLONE_FILTER\/\fR filter for use with \fB\-\-partial\-clone\fR [default: blob:none] .TP \fB\-\-use\-superproject\fR use the manifest superproject to sync projects; implies \fB\-c\fR .TP \fB\-\-no\-use\-superproject\fR disable use of manifest superprojects .TP \fB\-\-clone\-bundle\fR enable use of \fI\,/clone.bundle\/\fP on HTTP/HTTPS (default if not \fB\-\-partial\-clone\fR) .TP \fB\-\-no\-clone\-bundle\fR disable use of \fI\,/clone.bundle\/\fP on HTTP/HTTPS (default if \fB\-\-partial\-clone\fR) .SS repo Version options: .TP \fB\-\-repo\-url\fR=\fI\,URL\/\fR repo repository location ($REPO_URL) .TP \fB\-\-repo\-rev\fR=\fI\,REV\/\fR repo branch or revision ($REPO_REV) .TP \fB\-\-no\-repo\-verify\fR do not verify repo source code .SS Other options: .TP \fB\-\-config\-name\fR Always prompt for name/e\-mail .SS GITC options: .TP \fB\-f\fR MANIFEST_FILE, \fB\-\-manifest\-file\fR=\fI\,MANIFEST_FILE\/\fR Optional manifest file to use for this GITC client. .TP \fB\-c\fR GITC_CLIENT, \fB\-\-gitc\-client\fR=\fI\,GITC_CLIENT\/\fR Name of the gitc_client instance to create or modify. .PP Run `repo help gitc\-init` to view the detailed manual. .SH DETAILS .PP The 'repo gitc\-init' command is ran to initialize a new GITC client for use with the GITC file system. .PP This command will setup the client directory, initialize repo, just like repo init does, and then downloads the manifest collection and installs it in the \&.repo/directory of the GITC client. .PP Once this is done, a GITC manifest is generated by pulling the HEAD SHA for each project and generates the properly formatted XML file and installs it as \&.manifest in the GITC client directory. .PP The \fB\-c\fR argument is required to specify the GITC client name. .PP The optional \fB\-f\fR argument can be used to specify the manifest file to use for this GITC client.