git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Teach git-remote to update existing remotes by fetching from them

From
Shawn O. Pearce <spearce@spearce.org>
Date
Feb 19, 2007, 07:32 UTC
Message-ID
<20070219073238.GA30030@spearce.org>
In-Reply-To
<7virdybu9a.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
Show 6 quoted lines
> "Theodore Ts'o" <tytso@mit.edu> writes:
> 
> > This allows users to use the command "git remote update" to update all
> > remotes that are being tracked in the repository.
> 
> Sounds like a good idea.  Thanks.
<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. :)

Possible syntax:
	[remote "cs"]
		remote = cs-one
		remote = cs-two
	[remote "jc"]
		remote = origin
		remote = alt
</personalwishlist>
Obviously this is more work than Ted's nice little patch.  :)
-- 
Shawn.
Previous: Junio C HamanoNext: Alex Riesen
Message 3 of 8 in “Teach git-remote to update existing remotes by fetching from them”
  1. Teach git-remote to update existing remotes by fetching from themTheodore Ts'o, Feb 19, 2007
  2. Junio C HamanoFeb 19, 2007
  3. Shawn O. PearceFeb 19, 2007
  4. Alex RiesenFeb 19, 2007
  5. Jakub NarebskiFeb 19, 2007
  6. Theodore TsoFeb 19, 2007
  7. Junio C HamanoFeb 19, 2007
  8. Jakub NarebskiFeb 20, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.