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

Re: [PATCH] Fix git-for-each-refs broken for tags

From
Petr Baudis <pasky@suse.cz>
Date
Nov 18, 2006, 04:54 UTC
Message-ID
<20061118045431.GL7201@pasky.or.cz>
In-Reply-To
<7v4psxfjmw.fsf@assigned-by-dhcp.cox.net>
On Sat, Nov 18, 2006 at 05:45:11AM CET, Junio C Hamano wrote:
Show 5 quoted lines
> Thanks for noticing.
> 
> This is not like rev-list where we walk all over the map of
> ancestry graph, so it might be a simpler and better to keep
> the buffer than to keep duplicate copies of pieces.

I would rather not do that in any new code since it's gonna be a problem if you use this outside of the standalone command as part of libgit.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
The meaning of Stonehenge in Traflamadorian, when viewed from above, is:
"Replacement part being rushed with all possible speed."
Previous: Junio C Hamano
Message 3 of 3 in “Fix git-for-each-refs broken for tags”
  1. Fix git-for-each-refs broken for tagsPetr Baudis, Nov 18, 2006
  2. Junio C HamanoNov 18, 2006
  3. Petr BaudisNov 18, 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.