Hi, On Tue, 4 Jul 2006, Junio C Hamano wrote: > However, I am not sure how you are going to use that maximumSkew > variable. My idea was to continue traversing the merge base's ancestors, marking them UNINTERESTING, until hitting a commit which is maximumSkew older than the merge base (and not just stop at the merge base, as is the case right now, and neither continue traversing in eternity like suggested). This would not help _evil_ cases (i.e. intentional), but most certainly your regular clock skew in a Microsoft network. 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