Jeff King wrote: > What do we want to do with this? Probably I have already said too much about this topic, but here I go: > The third one is where we start defaulting things to "assume no more > than 1 day of clock skew by default", which can cause incorrect answers > in the face of skew. I think the default should be something that (just barely) works correctly for linux-2.6.git. > The fourth is just an illustrative patch for per-repo skew detection. I have been hoping for a chance to look these over, time hasn’t come my way yet. > I can work up a > "detect clock skew on clone and gc" patch based on it if we want to go > that way. That sounds very sane. Additional things to do (this is mostly a note to myself): - refuse to commit with a timestamp long before any parent - refuse to make a commit that would make the total slop too high? - check slop and warn about it in fsck (maybe your patch does this already) - document the maximum-total-slop and maximum-single-commit-slop rules! -- 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