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

RE: The merge from hell...

From
Linus Torvalds <torvalds@osdl.org>
Date
Feb 3, 2006, 05:45 UTC
Message-ID
<Pine.LNX.4.64.0602022139190.3462@g5.osdl.org>
In-Reply-To
<F7DC2337C7631D4386A2DF6E8FB22B3005EFE7FF@hdsmsx401.amr.corp.intel.com>
On Thu, 2 Feb 2006, Brown, Len wrote:
> 
> I can do 16 next time, or 22, or none
Actually, you can't do 22:
	/*
	 * Having more than two parents is not strange at all, and this is
	 * how multi-way merges are represented.
	 */
	#define MAXPARENT (16)
(commit-tree.c).

Now, admittedly you should literally need no more than to change that #define and recompile, but at least by default, git-write-tree won't accept more than 16 parents.

The 12-way merge was a bit over the top, but it worked. I'd suggest not beign quite _that_ aggressive in the future, though, but it's not a big deal.

One thing I'd ask for: would it be possible to have more descriptive branch names than just numbers? Even if you want to track it by bugzilla entry number, how about calling it "bugzilla-12345" instead?

I can make the educated guess that it's the bugzilla.kernel.org tracking number, but still.. I think it would make the changelog more readable and understandable to outsiders.

		Linus
Previous: Brown, LenNext: Junio C Hamano
Message 2 of 5 in “RE: The merge from hell...”
  1. Brown, LenFeb 3, 2006
  2. Linus TorvaldsFeb 3, 2006
  3. Junio C HamanoFeb 3, 2006
  4. get_sha1_1: allow octopus^12 to be properly parsed.Junio C Hamano, Feb 3, 2006
  5. Dave JonesFeb 3, 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.