On Jul 6, 2010, at 4:03 AM, Jonathan Nieder wrote: > At one point rev-list did require monotonic --- i.e., the committer > date of each commit had to be equal to or later than that of each of > its parents) with no clock skew but that was considered a bug and > fixed by v1.5.5-rc1~16 (Make revision limiting more robust against > occasional bad commit dates, 2008-03-17) You're right that it's been a while since git has run into problems with mild forms of clock skew (even Debian Stable is shipping v1.5.6) but I think it's better to times in the future if we can at all help it, and it's not like we're talking about a lot of extra complexity to guilt to test for this. > By the way, I think your idea to have commit warn about nonmonotonic > commit dates is a good one. We should also decide on a rule, > hopefully one the kernel repo obeys (30 days max skew? *crosses > fingers*) and make git fsck warn loudly about violations. Having git commit warn, absolutely. Unfortunately, there is already ~100 days of skew (see the earlier discusion on this thread by Jeff King) in the Linux kernel repo already... -- Ted -- 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