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
Junio C Hamano <junkio@cox.net>
Date
Feb 19, 2007, 20:09 UTC
Message-ID
<7vfy917vu3.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20070219125219.GD25490@thunk.org>
Theodore Tso <tytso@mit.edu> writes:
> ..., 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 am with you 100% on this one. Pushing to two separate places makes perfect sense, but fetching (or worse, pulling) from two separate places has certain "Huh?" factor in its semantics.

Previous: Theodore TsoNext: Jakub Narebski
Message 7 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.