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

Re: [RFC][PATCH] for_each_ref() returning heads in wrong order

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Sep 23, 2006, 17:20 UTC
Message-ID
<Pine.LNX.4.63.0609231919510.25853@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<20060923164759.GP8259@pasky.or.cz>
Hi,
On Sat, 23 Sep 2006, Petr Baudis wrote:
Show 8 quoted lines
> Dear diary, on Sat, Sep 23, 2006 at 06:36:21PM CEST, I got a letter
> where Petr Baudis <pasky@suse.cz> said that...
> > Using the #next branch I've now hit a problem with git-fetch-pack
> > master choosing refs/bases/master (I geuss created by StGIT) instead
> > of refs/heads/master. The old upload-pack returned the refs in the order
> > heads-tags-everything_else but the new one just goes for whatever order
> > readdir() returns them in (modulo merging with packed refs). I actually
> > can't see the difference that caused this right now, though.

Why don't you just specify (or match) "heads/refs/master", so that git-fetch-pack cannot choose anything wrong to begin with?

Ciao, Dscho

Previous: Petr BaudisNext: Petr Baudis
Message 3 of 6 in “for_each_ref() returning heads in wrong order”
  1. Petr BaudisSep 23, 2006
  2. Petr BaudisSep 23, 2006
  3. Johannes SchindelinSep 23, 2006
  4. Petr BaudisSep 23, 2006
  5. Linus TorvaldsSep 23, 2006
  6. Junio C HamanoSep 23, 2006

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.