Lines Matching full:repo
1 page.title=Repo command reference
27 <p>Repo usage takes the following form: </p>
28 <pre><code>repo COMMAND OPTIONS
30 <p>Optional elements are shown in brackets [ ]. Once Repo is installed, you can get information about any command by running </p>
31 <pre><code>repo help COMMAND
34 <pre><code>repo sync [PROJECT0 PROJECT1 ... PROJECTN]
35 repo sync [/PATH/TO/PROJECT0 ... /PATH/TO/PROJECTN]
39 <pre><code>$ repo init -u URL [OPTIONS]
41 <p>Installs Repo in the current directory. This creates a <code>.repo/</code> directory that contains Git repositories for the Repo source code and the standard Android manifest files. The <code>.repo/</code> directory also contains <code>manifest.xml</code>, which is a symlink to the selected manifest in the <code>.repo/manifests/</code> directory.</p>
54 <p><em>Note: For all remaining Repo commands, the current working directory must either be the parent directory of <code>.repo/</code> or a subdirectory of the parent directory.</em></p>
56 <pre><code>repo sync [PROJECT_LIST]
58 <p>Downloads new changes and updates the working files in your local environment. If you run <code>repo sync</code> without any arguments, it will synchronize the files for all the projects.</p>
59 <p>When you run <code>repo sync</code>, this is what happens:</p>
62 <p>If the project has never been synchronized, then <code>repo sync</code> is equivalent to <code>git clone</code>. All branches in the remote repository are copied to the local project directory.</p>
65 <p>If the project has already been synchronized once, then <code>repo sync</code> is equivalent to:</p>
75 <p>After a successful <code>repo sync</code>, the code in specified projects will be up to date with the code in the remote repository.</p>
89 <pre><code>repo upload [PROJECT_LIST]
91 <p>For the specified projects, Repo compares the local branches to the remote branches updated during the last repo sync. Repo will prompt you to select one or more of the branches that have not yet been uploaded for review.</p>
100 single commit, use git rebase -i before you run repo upload.</p>
101 <p>If you run repo upload without any arguments, it will search all the projects for changes to upload.</p>
108 <p>Use <code>repo upload --replace PROJECT</code> to open the change matching editor.</p>
115 [ 3022 ] c99883fe Teach 'repo upload --replace' how to add replacement patch se...
123 <pre><code>repo diff [PROJECT_LIST]
127 <pre><code>repo download TARGET CHANGE
131 <pre><code>$ repo download platform/build 23823
133 <p>A <code>repo sync</code> should effectively remove any commits retrieved via <code>repo download</code>. Or, you can check out the remote branch; e.g., <code>git checkout m/master</code>.</p>
136 <code>repo download</code> will be able to find it for all users, because of replication
139 <pre><code>repo forall [PROJECT_LIST] -c COMMAND
141 <p>Executes the given shell command in each project. The following additional environment variables are made available by <code>repo forall</code>:</p>
172 <pre><code>repo prune [PROJECT_LIST]
176 <pre><code>repo start BRANCH_NAME [PROJECT_LIST]
183 <pre><code>repo status [PROJECT_LIST]
186 <p>To see the status for only the current branch, run <code>repo status</code>. The status information will be listed by project. For each file in the project, a two-letter code is used:</p>
