From: Theodore Tso <tytso@mit.edu>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] Teach git-remote to update existing remotes by fetching from them
Date: Mon, 19 Feb 2007 07:52:19 -0500 [thread overview]
Message-ID: <20070219125219.GD25490@thunk.org> (raw)
In-Reply-To: <20070219073238.GA30030@spearce.org>
On Mon, Feb 19, 2007 at 02:32:38AM -0500, Shawn O. Pearce wrote:
> <personalwishlist>
>
> It would be nice to define "gang remotes". For example I want to
> be able to have:
>
> `git fetch cs` == `git fetch cs-one; git fetch cs-two`
> `git fetch jc` == `git fetch origin; git fetch alt`
>
> Why? Well, I often have multiple remotes setup to the *same*
> repository depending on the SSH hostname I want to use to access
> that repository. This has a lot to do with the way my firewalls
> are setup and where I'm physically connected at any given time.
>
> Yes, I really do have multiple remotes setup to the access the
> same (remote) physical disk. :)
Here are a couple of things that I'm thinking about doing with the
patch I submitted yesterday:
1) Change the configuration parameter from remote.fetch to
remotes.default.update, and let "git remote update" take a parameter,
"git remote update <name>", where it will look up the list of remotes
to fetch via remotes.<name>.update, and default <name> to "default" if
it is not specified.
2) In the case of <name> == default, if remotes.default.update does
not exist, it will update all remotes, skipping remotes where
remote.*.no_default_fetch is true. (This allows people who want to
omit certain special case remotes that only work if their connection
to the intranet is up, etc., to be able to set up something
convenientl; but for people who have more complex setups, they will
have to use the method specified in (1) above.
I thought about doing this via git-fetch, but (1) git-fetch.sh is
already way too complicated as it is, and I see that JC is in the
process of rewriting portions of it to C; by implementing in
git-remote.perl I avoided potential patch conflicts, and (2) fetching
groups of remotes would be overloading concepts for git-fetch, which
makes not only the implementation hard, but also the potential
semantics. i.e., what does this mean?
[remote "cs"]
remote = cs-one
remote = cs-two
url = git://git.kernel.org/pub/scm/git/git.git
fetch = +refs/heads/*:refs/remotes/origin/*
- Ted
next prev parent reply other threads:[~2007-02-19 13:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 4:00 [PATCH] Teach git-remote to update existing remotes by fetching from them Theodore Ts'o
2007-02-19 5:18 ` Junio C Hamano
2007-02-19 7:32 ` Shawn O. Pearce
2007-02-19 11:05 ` Alex Riesen
2007-02-19 13:21 ` Jakub Narebski
[not found] ` <20070219201111.GA3407@steel.home>
2007-02-20 15:24 ` Jakub Narebski
2007-02-19 12:52 ` Theodore Tso [this message]
2007-02-19 20:09 ` Junio C Hamano
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070219125219.GD25490@thunk.org \
--to=tytso@mit.edu \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=spearce@spearce.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.
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 NNTP newsgroup(s).