Re: [PATCH] Multiple refs from the same remote in one git fetch

From: Michael S. Tsirkin <mst@mellanox.co.il>
Date: Aug 14, 2006, 06:33 UTC
Message-ID: <20060814063309.GD21963@mellanox.co.il>
In-Reply-To: <7vzme7g8wt.fsf@assigned-by-dhcp.cox.net>

Quoting r. Junio C Hamano <junkio@cox.net>:

Show 20 quoted lines

> Subject: Re: [PATCH] Multiple refs from the same remote in one git fetch
> 
> "Michael S. Tsirkin" <mst@mellanox.co.il> writes:
> 
> > BTW, does it still look like it's worth it the effort to lift the restriction,
> > or does fixing the error message to something like
> > "no such remote or duplicate ref %s"
> > make more sense to you?
> 
> I have been hesitant to claim that it does not make any sense to
> use more than one tracking branch for the same remote branch,
> because the only reason I might say so is because I haven't
> thought of a good usage pattern to do so.
> 
> But apparently you do use more than one local branch to keep
> track of one remote branch.  How do you use it for?  Do you feel
> it is a good feature to be able to do that, or do you think it
> is just a mistake and more sensible error message is what we
> would really want?
>

Well, what I was *trying* to do is simply add a more descriptive name for the linus master branch to my existing tree. So it seemed like an obvious idea to add

Pull: master:origin
Pull: master:linus_master

On a more theoretical level, in a shared repository development style, one might imagine several people who want the branch to be called differently. Another reason might be scripts using specific branch names where you might want to be free to decide where a specific branch name points to.

Yea, I still feel it would be a good feature to have - I just wanted to check there's no opposition to this.

-- 
MST