Re: [PATCH] git-clone: use wildcard specification for tracking branches

From: Jakub Narebski <jnareb@gmail.com>
Date: Dec 16, 2006, 09:39 UTC
Message-ID: <em0eo3$122$1@sea.gmane.org>
In-Reply-To: <7vfybgjj7k.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano wrote:

Show 8 quoted lines

> This stops enumerating the set of branches found on the remote
> side when a clone was made in the configuration file.  Instead,
> a single entry that maps each remote branch to the local
> tracking branch for the remote under the same name is created.
> 
> Doing it this way not only shortens the configuration file, but
> automatically adjusts to a new branch added on the remote side
> after the clone is made.

[...]

Does this deal with non-fast-forward branches like 'pu'? Does it add $head_points_at at the beginning, before glob... wait, this is not needed if there is branch.$head_points_at.merge. But perhaps it still would be better to have:

  [remote "origin"]
        url   = git://git.kernel.org/pub/scm/git/git.git
        fetch = refs/heads/master:refs/remotes/origin/master
        fetch = refs/heads/*:refs/remotes/origin/*
        fetch =+refs/heads/pu:refs/remotes/origin/pu

  [branch "master"]
        remote = origin
        merge  = refs/heads/master ;# full spec of remote branch

But this is very nice. Thanks.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git