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

Re: [RFH] bug in unpack_trees

From
Linus Torvalds <torvalds@linux-foundation.org>
Date
Mar 4, 2008, 21:31 UTC
Message-ID
<alpine.LFD.1.00.0803041325370.12253@woody.linux-foundation.org>
In-Reply-To
<20080304115940.GA5260@sigill.intra.peff.net>
On Tue, 4 Mar 2008, Jeff King wrote:
>
> I am tracking down a bug in unpack_trees, but I can't seem to find the
> exact problem; I'm hoping to get help from people who have touched this
> code a bit more than I have.

Ok, I haven't (the blame for that unpack_trees function lies mainly at Dscho, I think ;), and now that I'm looking at it more closely I really don't think unpack_trees() is salvageable.

I tried. I can't make it work.

The only really sane way to traverse trees in parallel is with the walk-tree.c functionality (ie using "traverse_trees()"), which is quite straightforward and rather simple, and which I can pretty much guarantee works.

In contrast, the things that unpack_trees() does to try to figure out how to mix in the index into the pot really doesn't work.

I'll take a good hard look at trying to convert users of unpack_trees() into traverse_trees(), or perhaps even convert "unpack_trees()" itself.

		Linus
Previous: Jeff KingNext: Daniel Barkalow
Message 2 of 9 in “[RFH] bug in unpack_trees”
  1. Jeff KingMar 4, 2008
  2. Linus TorvaldsMar 4, 2008
  3. Daniel BarkalowMar 5, 2008
  4. Linus TorvaldsMar 5, 2008
  5. Linus TorvaldsMar 6, 2008
  6. Linus TorvaldsMar 8, 2008
  7. Daniel BarkalowMar 8, 2008
  8. Jeff KingMar 13, 2008
  9. John GoerzenMar 14, 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.