Re: cogito "origin" vs. HEAD

From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: May 3, 2005, 07:13 UTC
Message-ID: <1115104408.6156.100.camel@gaston>
In-Reply-To: <20050503064943.GB10244@pasky.ji.cz>

Show 5 quoted lines

> when accessing the remote repository, Cogito always looks for remote
> refs/heads/master first - if that one isn't there, it takes HEAD, but
> there is no correlation between the local and remote branch name. If you
> want to fetch a different branch from the remote repository, use the
> fragment identifier (see cg-help cg-branch-add).

Ok, that I'm getting. So then, what happen of my local refs/heads/<branchname> and refs/heads/master/ ? I'm still a bit confused by the whole branch mecanism... It's my understanding than when I cg-init, it creates both "master" (a head without matching branch) and "origin" (a branch + a head) both having the same sha1. It also checks out the tree.

Now, when I cg-update origin, what happens exactly ? I mean, I know it's pulls all objects, then get the master from the remote pointed by the origin branch, but then, I suppose it updates both my local "origin" and my local "master" pointer, right ? I mean, they are always in sync ? Or is this related to what branch my current checkout is tracking ?

Ben.