From: Jeff King <peff@peff.net>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: git@vger.kernel.org
Subject: Re: Per-remote tracking branch
Date: Thu, 24 Sep 2009 02:29:12 -0400 [thread overview]
Message-ID: <20090924062911.GC24486@coredump.intra.peff.net> (raw)
In-Reply-To: <vpq4or48bux.fsf@bauges.imag.fr>
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
next prev parent reply other threads:[~2009-09-24 6:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 15:29 Per-remote tracking branch Matthieu Moy
2009-09-24 6:29 ` Jeff King [this message]
2009-09-24 11:10 ` Matthieu Moy
2009-09-24 11:25 ` Björn Steinbrink
2009-09-24 11:35 ` Björn Steinbrink
2009-09-24 16:00 ` Matthieu Moy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090924062911.GC24486@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).