Markus Wanner <[EMAIL PROTECTED]> writes: > I'm just proposing to check the date and warn the user if it obviously > doesn't match. It would help making that meta-information more reliable, > nothing more, nothing less.
If there is no global shared clock, then developers working in different time zones can easily commit revisions to a shared server that have timestamps using local times that appear to be "out of order" with respect to each other. Why would you want to warn about that? On the other hand, there are such things as global clocks; we use them all the time at NASA. If each developer on a team commits to configuring their computer such that the functions "local_to_UTC" and "UTC_to_local" work properly, monotone could support an option to use UTC times for timestamps. TAI might be a better global time choice, since it doesn't do leap seconds, and hence is monotonic. -- -- Stephe _______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel