Re: ia64 git pull

From: Petr Baudis <>
Date: 2005-04-22 08:53:24
Dear diary, on Thu, Apr 21, 2005 at 11:55:43PM CEST, I got a letter
where told me that...
> I can't quite see how to manage multiple "heads" in git.  I notice that in
> your tree on that .git/HEAD is a symlink to heads/master ...
> perhaps that is a clue.
> I'd like to have at least two, or perhaps even three "HEADS" active in my
> tree at all times.  One would correspond to my old "release" tree ... pointing
> to changes that I think are ready to go into the Linus tree.  A second would
> be the "testing" tree ... ready for Andrew to pull into "-mm", but not ready
> for the base. The third (which might only exist in my local tree) would be
> for changes that I'm playing around with.

To set up that, go into your "master" working directory, and do:

	git fork release ~/release
	git fork testing ~/testing

Then in ~/release or ~/testing respectively, you have working trees for
the respective branches.

> I can see how git can easily do this ... but I don't know how to set up my
> public tree so that you and Andrew can pull from the right HEAD.

Currently, git pull will _never_ care about your internal heads
structure in the remote repository. It will just take HEAD at the given
rsync URI, and update the remote branch's head in your repository to
that commit ID.  This actually seems to be one of the very common
pitfalls for people.

The way to work around that is to setup separate rsync URIs for each of
the trees. ;-) I think I will make git-pasky (Cogito) accept also URIs
in form


which will allow you to select the particular branch in the given
repository, defaulting to the "master" branch.

Would that work for you?

				Petr "Pasky" Baudis
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to
More majordomo info at
Received on Thu Apr 21 18:53:46 2005

This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:37 EST