[merge] 1ms resolution for commit timestamps

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John Arbash Meinel wrote:
> Aaron Bentley wrote:
> 
>>>What would be the problem with having multiple commits with the same
>>>timestamp?

> No specific problem with it. Just that we have more information than
> that. So it doesn't really need to be thrown away.
> 1ms seemed like a decent compromise, 1s seemed too restrictive, and not
> restricting at all seemed to open us up to floating point precision
> bugs.

The timestamp is human-facing data, and even 1s accuracy is probably
excessive for that, so I'd lean toward 1s precision.  But I don't feel
strongly.  I was just worried for a second that we were acually using
the timestamp somewhere instead of using ancestry.  Anyhow, I don't feel
strongly about 1s-precision, but avoiding rounding errors seems like a
Good Thing.  +1.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEvT7B0F+nu1YWqI0RAm9wAJ9uyV57P7O/7dZcYbLSlGydnmacEwCeM2bA
hm0FblstmRb5EgLGzO5iDdE=
=OPlY
-----END PGP SIGNATURE-----