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

Re: Remotes order in "git remote update"

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 9, 2008, 10:38 UTC
Message-ID
<7vbq5op4gt.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<2008-03-09-11-22-34+trackit+sam@rfc1149.net>
Samuel Tardieu <sam@rfc1149.net> writes:
> It looks like remote repositories are ordered alphabetically by their
> local names when doing a "git remote update".

Yeah, it is an unfortunate consequence of the Perl implementation that uses a hash to record remote and then try to give a stable ordering by sorting keys. The command originally was never intended for working on more than one remote, but addition of "remote update" could have been done to follow the order in the configuration.

I think the reimplementaiton in 'next' that will hopefully be in 1.5.5 will keep the list of remotes in the order read from the config.

Previous: Samuel TardieuNext: Samuel Tardieu
Message 2 of 9 in “Remotes order in "git remote update"”
  1. Samuel TardieuMar 9, 2008
  2. Junio C HamanoMar 9, 2008
  3. Samuel TardieuMar 9, 2008
  4. Johannes SchindelinMar 9, 2008
  5. Junio C HamanoMar 10, 2008
  6. Johannes SchindelinMar 10, 2008
  7. Samuel TardieuMar 10, 2008
  8. Johannes SchindelinMar 10, 2008
  9. Junio C HamanoMar 10, 2008

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.