Yes, there should be a cupcake branch for all android projects except
the kernel.
Issue a git branch -a to see the list of branches in a project. If you
checked out the tree with -b cupcake then you should be seeing a branch
name m/cupcake below * (no branch) which typically says you tree is
based of cupcake manifest.

For your second question, I have taken the example of the git project
platform/build.
http://android.git.kernel.org/?p=platform/build.git;a=summary

If you scroll down the above page you can see

3 weeks ago master shortlog | log | tree
6 weeks ago donut shortlog | log | tree
6 weeks ago cupcake shortlog | log | tree
4 months ago cdma-import shortlog | log | tree
7 months ago release-1.0 shortlog | log | tree

which are typically the branches for this project platform/build.

I'm not sure about the heads you are referring to here.

Thanks.
Sridhar.

ganganwen wrote:
> Hi, all
> I just downloaded the source using the following command:
> $ repo init -u git://android.git.kernel.org/platform/manifest.git -b cupcake
> $ repo sync  
>
> So, Does this mean that I am using cupcake branch?
> Is there a cupcake branch in every git project in the source?
> but when I run git branch, it said: no branch
> $ git branch
> * (no branch)
>
> Another question: how do I know what branches are there?
> I see through git web:
> http://android.git.kernel.org/?p=kernel/common.git;a=summary 
> and some heads are there, does "heads" means "branches"?
> heads 
> 37 hours agoandroid-2.6.29shortlog | log | tree
> 9 days agoandroid-goldfish-2.6.29shortlog | log | tree
> 2 months agoandroid-2.6.27shortlog | log | tree
> 4 months agoandroid-goldfish-2.6.27shortlog | log | tree
> 7 months agoandroid-2.6.25shortlog | log | tree
>
>
>  what the relationship between those branches and the branch using in "repo 
> -b branch"?
> thanks
>
> >
>
>   


--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---

Reply via email to