> Each commit object in git records two timestamps. When the > author made that change, and when the change was made into a > commit object in _some_ repository. Perhaps git should record three(+) timestamps, adding when the change was committed into this repository? Last weekend there was a committ in Linus' kernel tree with a timestamp ~2 days into the future, which could be a problem in a scenario involving when an important bug fix was merged/published in Linus' kernel tree, situations like that should be impossible. How can git be said to keep an accurate record of history if time is uncertain? -Matt __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - 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