Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > I tested git-merge-recur vs. git-merge-recursive on the linux-2.6 > repository last night. It contains 2298 two-head merges. _All_ of them > come out identically with -recur as compared to -recursive (looking at > the resulting index only). Nice. > That was the good news. The bad news is: it _seems_, that -recur is only > about 6x faster than -recursive, not 10x, and this number becomes smaller, > the longer the merge takes. So I see a startup effect here, probably. Recreating the tip of "next" (10a6653) might be fun. I do not know why, but it ended up having 14 merge bases. The speed-up is about 6x, and the resulting half-merge is worse than recursive (not using rerere cache). - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html