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

Re: Remotes order in "git remote update"

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Mar 10, 2008, 11:11 UTC
Message-ID
<alpine.LSU.1.00.0803101211000.3975@racer.site>
In-Reply-To
<7vbq5nm8k1.fsf@gitster.siamese.dyndns.org>
Hi,
On Sun, 9 Mar 2008, Junio C Hamano wrote:
Show 6 quoted lines
> We _might_ want to start guaranteeing some orders by documenting, but I 
> do not think it is necessary.  Does "git config" and "git remote" code 
> even guarantee the order the newly added ones are stored in the 
> $GIT_DIR/config file, and is it by design and specified in the 
> documentation, or it is by accident and happens to be the way the code 
> is written?

git_config_set() appends to the end of the config if the section it tries to edit did not exist yet. However, this is just an implementation detail, no design decision.

Ciao, Dscho

Previous: Junio C HamanoNext: Samuel Tardieu
Message 6 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.