Hi, On Wed, 5 Jul 2006, A Large Angry SCM wrote: > If grafts in your repository create a cycle, the misbehavior of merge-base > should be among the least of your concerns. Right. BUT grafts can be very helpful to connect branches which were independently imported into git. And in these cases, the clockSkew really is no clockSkew. But in that case, the generation number would have to be recalculated also. Anyway, I think that it should be a configurable, which defaults to off, i.e. in the normal case merge-base should behave as it does now. And if we have that configurable, we might as well take the safe but dumb approach to just traverse _everything_. Ciao, Dscho - : 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