--- Linus Torvalds <torvalds@xxxxxxxx> wrote: > The actual action happened at 8:30. And git tracks only truth. It doesn't > rewrite the truth afterward. So the separate action of replication is not tracked? Replication/sub merges are denied the possibility of "truth"? To be clear I think there are actually two separate though semi-related issues: - 1. release/replication time of a mirrored private --> public repo - 2. A repo's commit order being inconsistent with local time order My questions are primarily focused on #2. Last weekend even your private repo's commit order was out of sync with your local time order because a remote git server's time was grossly misconfigured, right? Integrity wise that shouldn't happen. I am merely asking if tracking commits/merges using local repo time could solve both issues? If the local merge time information is already available in the ref-log then gitweb.cgi might only need to be made aware of it. -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