How to display available branches in Android source tree?
Solution 1
It doesn't seem to be possible using the "repo" script, but you can query the list of available branches using git:
$ git clone https://android.googlesource.com/platform/manifest.git
$ cd manifest
$ git branch -r
If you don't want to clone the repository just for this, you can see the branches on the web interface.
Solution 2
The quickest way to list available branches without cloning/downloading anything is this one-liner:
$ git ls-remote -h https://android.googlesource.com/platform/manifest.git
Solution 3
The manifests are already checked out as part of the repo init process. To get a list of available branches, (from your android repo checkout root), use this command:
git --git-dir .repo/manifests/.git/ branch -a
Solution 4
See list of "Codenames, Tags, and Build Numbers" at http://source.android.com/source/build-numbers.html
git access is refused
Solution 5
For the repository you have perform repo sync
. You can find them in your local directory .repo/manifests
. Suppose you check aosp
to ~/aosp
.
$ cd ~/aosp/.repo/manifests
$ git branch -r
theactiveactor
Updated on June 11, 2020Comments
-
theactiveactor almost 4 years
Following directions on Android's main website to pull down sources, I'm looking at this command to initialize repo for the cupcake branch:
repo init -u git://android.git.kernel.org/platform/manifest.git -b cupcake
How can I view all available branches besides cupcake, i.e eclair, donut, etc...?
-
Cristian Ciupitu over 13 yearsGit web interface for the people who don't want to clone the git repository just to see what branches are available.
-
João Kleberson about 12 yearsIt seems that the location of manifests git location has changed: "git --git-dir .repo/manifests.git/ branch -a"
-
gsgx over 11 years@CristianCiupitu Your link seems to be broken. Here's the new link: android.googlesource.com/platform/manifest
-
Cristian Ciupitu over 11 years@gsingh2011: thanks! Now I have the reputation required to mention the location in the answer, so that comments don't pile up on every change.