Re: Getting new branches from remote repo.

From: Junio C Hamano <junkio@cox.net>
Date: Nov 13, 2006, 04:49 UTC
Message-ID: <7v8xigar36.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <6e1787fe0611122033p49671e13xf5b7f95beeba8b06@mail.gmail.com>

"Alexander Litvinov" <litvinov2004@gmail.com> writes:

Show 7 quoted lines

> I have a trouble I don't know how to solve. When I am cloning remote
> repo I automatically get all it's branches stored at my repo (they are
> listed at .git/remotes/origin). When someone adds new branch(es) to
> remote repo git pull (git fetch) does not automatically add them to my
> repo. I have a tool to list all remote branches (git ls-remote --heads
> origin) but I can't find how to add interesting (or all) branches to
> by repo.

After finding out $that_new_branch's name, add either

	Pull: refs/heads/$that_new_branch:refs/heads/$that_new_branch

or if you are in "separate remote" school, then perhaps

	Pull: refs/heads/$that_new_branch:refs/remotes/origin/$that_new_branch

to .git/remotes/origin and running git fetch would give you what you want, I think.

> By the way, how can I clone remote repo created by cloning another
> repo using git clone --use-separate-remotes ? Even git ls-remote
> --heads origin does not show all branches taken from that another
> repo.

Well, the point of "separate remote" is not to pollute local heads/ namespace with refs that merely track remote repository, so if you say "ls-remote --heads" you would not see them. They are not "heads" in that repository.

You would still see them if you say "ls-remote" without --heads.