Lines Matching full:branch
51 <p><code>-b</code>: specify a revision, i.e., a particular manifest-branch.</p>
67 git rebase origin/BRANCH
69 <p>where <code>BRANCH</code> is the currently checked-out branch in the local project directory. If the local branch is not tracking a branch in the remote repository, then no synchronization will occur for the project.</p>
79 <p><code>-d</code>: switch specified projects back to the manifest revision. Helpful if the project is currently on a topic branch, but the manifest revision is temporarily needed.</p>
105 <p>Make sure the updated branch is the currently checked out branch.</p>
112 <pre><code># Replacing from branch foo
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>
153 <p><code>REPO_LREV</code> is the name of the revision from the manifest, translated to a local tracking branch. Used if you need to pass the manifest revision to a locally executed git command.</p>
178 <p>Begins a new branch for development, starting from the revision specified in the manifest.</p>
180 <p>The <code>PROJECT_LIST</code> specifies which projects will participate in this topic branch. </p>
185 <p>Compares the working tree to the staging area (index) and the most recent commit on this branch (HEAD) in each project specified. Displays a summary line for each file where there is a difference between these three states.</p>
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>
