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

Removal of "--merge-order"?

From
Linus Torvalds <torvalds@osdl.org>
Date
Feb 24, 2006, 16:32 UTC
Message-ID
<Pine.LNX.4.64.0602240824110.3771@g5.osdl.org>
I just tested it again, and
	git-rev-list --merge-order HEAD
takes an inordinate amount of time:
	real    5m1.139s
	user    4m59.504s
	sys     0m1.220s

and that's on a reasonably fast machine (not my fastest, but no slouch by any measure - my fastest machine I'm not allowed to really benchmark publicly ;)

It may be a cool algorithm, but it's essentially useless on any bigger tree. And nobody uses it, since "--topo-order" gives the guarantees that people really care about, and finishes in 0.537 seconds on the same machine with the same tree.

It also depends on the openssh "bignum" stuff, which means that any machine where we just rely on our own SHA1 implementation and don't use openssh doesn't have the flag anyway.

In other words, I'd really prefer if it was gone. Some of the things I might do to git-rev-list would be much simpler if I didn't have to worry about merge-order, and the way it interfaces with the rest of git-rev-list.

Comments?
			Linus
Next: Randy.Dunlap
Message 1 of 9 in “Removal of "--merge-order"?”
  1. Linus TorvaldsFeb 24, 2006
  2. Randy.DunlapFeb 24, 2006
  3. Linus TorvaldsFeb 24, 2006
  4. Ryan AndersonFeb 24, 2006
  5. Randy.DunlapFeb 24, 2006
  6. Linus TorvaldsFeb 24, 2006
  7. Randy.DunlapFeb 24, 2006
  8. Johannes SchindelinFeb 24, 2006
  9. Junio C HamanoFeb 24, 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.