How does repo know from where to update its manifest?

[Guillaume Parent]

Hey,

I'm trying to setup my own ROM source tree, and using repo (wonderful tool
by the way) I've slowly learning how to properly branch off projects and
make it all work.

One last thing remains, the actual manifest repo.

From what I understand, the actual repository to update is .repo/manifests.

Does it just pull origin/<branch> where <branch> is what you put when you
repo init (for the -b option), and master if you didn't specify a branch?

If it helps, what I want to accomplish is an "ics" and a "jellybean"
branch, where the former would fork all of its repos from tag
android-4.0.4r2.1 and the latter from android-4.1.1r1. My manifest project
would then have the same two branches. I would then commit extra updates to
jellybean and ics directly, and branch off a release when necessary (that
release would be tagged and available somehow from a manifest or a manifest
branch).

Thanks,

[Shawn Pearce]

Post by Guillaume Parent
I'm trying to setup my own ROM source tree, and using repo (wonderful tool
by the way) I've slowly learning how to properly branch off projects and
make it all work.
One last thing remains, the actual manifest repo.
From what I understand, the actual repository to update is
.repo/manifests. Does it just pull origin/<branch> where <branch> is what
you put when you repo init (for the -b option), and master if you didn't
specify a branch?

Yes.