Re: Trying to Update All Heads of a Repository

From: Daniel Barkalow <barkalow@iabervon.org>
Date: Nov 4, 2005, 23:47 UTC
Message-ID: <Pine.LNX.4.64.0511041745480.25300@iabervon.org>
In-Reply-To: <7vy8453zhu.fsf@assigned-by-dhcp.cox.net>

On Thu, 3 Nov 2005, Junio C Hamano wrote:

Show 17 quoted lines

> Jon Loeliger <jdl@freescale.com> writes:
> 
> > First, I have this, because it came with a git-clone:
> >
> >     % cat .git/remotes/origin
> >     URL: rsync://rsync.kernel.org/pub/scm/git/git.git
> >     Pull: master:origin
> >
> > I don't know how to say "Grab all the updates for
> > all the heads for which I have heads in my .git/refs".
> 
> My "guinea pig" repository has this in $GIT_DIR/remotes/origin:
> 
>         URL: git://git.kernel.org/pub/scm/git/git.git
>         Pull: master:origin
>         Pull: +pu:pu
>         Pull: maint:maint

Shouldn't approximately this be what git-clone sets up for you? If it's getting those heads initially, it should keep the information for future use. The only thing it wouldn't know would be the "+" on pu.

On the "pu" issue, maybe "pu" shouldn't be a branch, but should be something different, like a tag. I think, actually, that a tag would describe "pu" pretty well: no development happens on its line; rather, development happens elsewhere (topic branches), and a merge of some of them is then released as being interesting. What is interesting as "pu" today isn't necessarily related to yesterday or tomorrow. Then you wouldn't exactly be rebasing things all the time, but you'd instead be marking different and unrelated commits in the same way at different times. (Probably need to do more to handle the case where a tag ref changes and define the semantics properly)

	-Daniel
*This .sig left intentionally blank*