On Sat, 21 Jul 2007, Jeff King wrote: > > Interestingly, I repeatably get the exact same error but with a > different commit: > > 7ed40918a386afc2e14a6d3da563ea6d13686c25 > > which looks like a totally uninteresting commit. It seems to depend on the path limiter. With "arch/i386", I get the 7ed409 one, with "arch/i386 arch/x86_64" I get a complaint about 57d1c91fa. In neither case do I see the reason. But I think I found a clue. One thing special about that 57d1c91fa is that when you do git log --topo-order --parents --pretty=one arch/i386/ arch/x86_64/ and search for it, it first shows up as a parent for commit 9fdb62af92: and not just _one_ parent, but three! So it looks like the parent simplification is broken, and maybe gitk is unhappy for that reason. The same is true of 7ed40918a38, btw, so yeah, I think that's it. Junio, didn't we have some parent simplification patches recently? Linus - 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
