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

Re: [RFC/PATCH] commit-tree: bump MAX_PARENTS to 128

From
Jeff King <peff@peff.net>
Date
Feb 27, 2007, 08:19 UTC
Message-ID
<20070227081933.GA13021@coredump.intra.peff.net>
In-Reply-To
<7vr6scj9qt.fsf@assigned-by-dhcp.cox.net>
On Tue, Feb 27, 2007 at 12:16:42AM -0800, Junio C Hamano wrote:
> But as Shawn pointed out, Octopus makes bisect less (much less)
> efficient for the end users, I tend to think the current 16 is
> already insanely large.

Did you look at my "why I need a huge octopus" description? Is there a better way to do it? Should I simply do a bunch of pair-wise merges? I'll almost certainly never bisect it, but the octopus "looks right" in gitk (though I have to admit, it's really not _that_ big a deal -- it's almost more readable to look at pairwise merges anyway).

-Peff
Previous: Junio C HamanoNext: Junio C Hamano
Message 5 of 12 in “commit-tree: bump MAX_PARENTS to 128”
  1. commit-tree: bump MAX_PARENTS to 128Jeff King, Feb 26, 2007
  2. Shawn O. PearceFeb 26, 2007
  3. Johannes SchindelinFeb 26, 2007
  4. Junio C HamanoFeb 27, 2007
  5. Jeff KingFeb 27, 2007
  6. Junio C HamanoFeb 27, 2007
  7. Jeff KingFeb 27, 2007
  8. Junio C HamanoFeb 27, 2007
  9. Andy ParkinsFeb 27, 2007
  10. Jeff KingFeb 27, 2007
  11. Jakub NarebskiFeb 27, 2007
  12. Johannes SchindelinFeb 27, 2007

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.