RE: Finer timestamps and serialization in git

From: Jason Pyeron <jpyeron@pdinc.us>
Date: May 15, 2019, 20:28 UTC
Message-ID: <023b01d50b5c$cbd3cd90$637b68b0$@pdinc.us>
In-Reply-To: <ae62476c-1642-0b9c-86a5-c2c8cddf9dfb@gmail.com>

(please don’t cc me)

Show 5 quoted lines

> -----Original Message-----
> From: Derrick Stolee
> Sent: Wednesday, May 15, 2019 4:16 PM
> 
> On 5/15/2019 3:16 PM, Eric S. Raymond wrote:

<snip/> I disagree with many of Eric's reasons - and agree with most of Derrick's refutation. But

> 
> Changing the granularity of timestamps requires changing the commit format,
> which is probably a non-starter.

is not necessarily true. If we take the below example:

committer Name <user@domain> 1557948240 -0400

and we follow the rule that:

1. any trailing zero after the decimal point MUST be omitted
2. if there are no digits after the decimal point, it MUST be omitted

This would allow:

committer Name <user@domain> 1557948240 -0400 committer Name <user@domain> 1557948240.12 -0400

but the following are never allowed:

committer Name <user@domain> 1557948240. -0400 committer Name <user@domain> 1557948240.000000 -0400

By following these rules, all previous commits' hash are unchanged. Future commits made on the top of the second will look like old commit formats. Commits coming from "older" tools will produce valid and mergeable objects. The loss precision has frustrated us several times as well.

Respectfully,

Jason Pyeron