On Tue, Sep 15, 2009 at 05:29:58PM +0200, Matthieu Moy wrote:
> Is there a way, with Git, to specify a tracking branch on a per-remote
> basis?
I don't think so, and I'm not sure there is an easy way to extend the
current configuration scheme. Adding multiple config options like this:
[branch "master"]
remote = origin
merge = refs/heads/master
remote = alternate
merge = refs/heads/master
looks a bit hack-ish to me, as there is an implicit correlation between
the ordering of 'merge' entries and 'remote' entries.
And it feels a little backwards. When I say "git pull foo", I would find
it equally likely to discover the pulled branch under "remote.foo" as it
would to find it under "branch.master". Of course, in either case, you
have to combine the context (current branch _and_ selected remote)
to come up with the actual information. So I guess either is "equally
correct" in a sense.
Anyway, mostly just my idle speculation.
-Peff
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html