From: Luben Tuikov <ltuikov@yahoo.com>
Date: Sat, 06 Jan 2007 00:16:57 GMT
Subject: Re: New way of tracking remote branches -- question
Message-ID: <224619.92262.qm@web31810.mail.mud.yahoo.com>
In-Reply-To: <7vzm8xcbcp.fsf@assigned-by-dhcp.cox.net>

--- Junio C Hamano <junkio@cox.net> wrote:
> Luben Tuikov <ltuikov@yahoo.com> writes:
> 
> > I can see that the remote heads are where they are supposed to be
> > but no local tracking heads are created (by default).  I had
> > to do this manually.
> >
> > Old behavior was that git did that for you automatically.
> > So I suppose this is another newbie protection.
> 
> A very fuzzily stated question which is hard to answer, but I do
> not think it is another newbie protection, if it apparently is
> actively hurting you.  Also the documentation may need to be
> updated to teach you enough about how to achieve what you want.
> 
> You can see where remote heads are by doing what?  ls-remote?
> "Old behaviour" for what configuration?
> 
> A fresh clone made with a recent version sets things up to track
> all remote branches from the repository you cloned from under
> remotes/origin/, and it even tracks new ones as they are added
> at the remote, so you probably are doing something different
> from the default configuration that has:
> 
>     remotes.origin.fetch = +refs/heads/*:refs/remotes/origin/*

That's exactly what I have, but "git branch" shows only "master".
The other branches are indeed in refs/remotes/origin/ but I want
them in refs/heads/ so I had to do that manually by creating
the head and add this into .git/config.

Old behavior was more _convenient_.

    Luben