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

Bottlenecks in git merge

From
PEPeter Eriksen <s022018@student.dtu.dk>
Date
Jan 31, 2006, 21:33 UTC
Message-ID
<20060131213314.GA32131@ebar091.ebar.dtu.dk>
Hello, 

In connection with Ian Molton's question about merge have I played a little with 'git merge' on the kernel sources. What I find is that a merge can take quite some time, but I'm not sure where that time exactly goes to. Here are the times I got:

Recursive (default): 4m22.282s Resolve (-s resolve): 3m23.548s

What is taking so long?
Regards,
Peter

==============================>8================== #!/bin/sh # Run from linux-2.6

change_readme() {
	sed -i "s/are much better/are better/" README
}

git checkout -f master git branch -d test git checkout -b test v2.6.12 change_readme git commit -a -m "Work, work, work" time git merge $STRATEGY "Merging happily." HEAD v2.6.15

Next: Junio C Hamano
Message 1 of 11 in “Bottlenecks in git merge”
  1. Peter EriksenJan 31, 2006
  2. Junio C HamanoJan 31, 2006
  3. Petr BaudisJan 31, 2006
  4. Junio C HamanoFeb 1, 2006
  5. Linus TorvaldsJan 31, 2006
  6. Petr BaudisFeb 1, 2006
  7. Linus TorvaldsFeb 1, 2006
  8. Petr BaudisJan 31, 2006
  9. read-tree --aggressiveJunio C Hamano, Feb 4, 2006
  10. Peter EriksenFeb 4, 2006
  11. Junio C HamanoFeb 4, 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.