StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>First, repo init creates the <code>.repo</code> directory, clones the git repository <a href="https://android.googlesource.com/tools/repo" rel="noreferrer">https://android.googlesource.com/tools/repo</a> to <code>.repo/repo</code>, and the git repository specified with the <code>-u</code> option to a bare repository at <code>.repo/manifests.git</code>. After that, it creates the <code>.repo/manifests</code> directory, converts it into a git repository through creating symbolic links from <code>.repo/manifests/.git</code> to <code>.repo/manifests.git</code>. It then checks out the branch specified in <code>-b</code>, and creates a symbolic link <code>.repo/manifest.xml</code> pointing to the specified file (<code>-m</code> option) in <code>.repo/manifests</code>, by default <code>.repo/manifests/default.xml</code>. </p> <p>Roughly as follows:</p> <pre> repo init -u $URL -b $BRANCH -m $MANIFEST -------------------- mkdir .repo; cd .repo git clone https://android.googlesource.com/tools/repo git clone --bare $URL manifests.git mkdir -p manifests/.git; cd manifests/.git for i in ../../manifests.git/*; do ln -s $ı .; done cd .. git checkout $BRANCH -- . cd .. ln -s manifests/$MANIFEST manifest.xml </pre> <p>You can trace what really happens with <code>repo --trace init ...</code></p> <p>Then, repo sync clones git repositories to <code>.repo/projects</code> for each project in <code>manifest.xml</code> and <code>local_manifest.xml</code>, creates working directories with <code>.git</code> having symlinks to the corresponding bare repository, checks out the branch specified in the manifest, and updates <code>.repo/project.list</code>. The case where the projects are already there is slightly different, essentially performing a <code>git pull --rebase</code>.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload