Re: New way of tracking remote branches -- question

From: Junio C Hamano <junkio@cox.net>
Date: Jan 5, 2007, 23:17 UTC
Message-ID: <7vzm8xcbcp.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <776323.21089.qm@web31808.mail.mud.yahoo.com>

Luben Tuikov <ltuikov@yahoo.com> writes:

Show 6 quoted lines

> 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/*