Re: Millisecond precision in timestamps?
- From
- David Lang <david@lang.hm>
- Date
- Nov 28, 2012, 00:22 UTC
- Message-ID
- <alpine.DEB.2.02.1211271620220.16794@nftneq.ynat.uz>
- In-Reply-To
- <20121128001231.GA27971@thyrsus.com>
On Tue, 27 Nov 2012, Eric S. Raymond wrote:
Show 13 quoted lines
> Shawn Pearce <spearce@spearce.org>: >> Well... if we added a fractional seconds to a commit, older versions >> of Git will scream loudly and refuse to work with the new commit. That >> would create a fork of Git. > > So much for that idea, I guess. > > Unless..I don't know how git's database representations work. Are they > version-stamped in any way? If so, some slightly painful hackery would > get around that problem. > > I'm being exploratory, here. No proposal to code anything is in the > offing.
Apologies if this was covered earlier in the thread (I missed the beginning)
remember that git is dealing with timestamps generated across different machines, and since the times are not assumed to be in sync, let alone to the millisecond level, there's not much value to git in that level of presision.
git routinely deals with timestamps that are off by days. If the timestamps are within a minute or so, you are in pretty good shape.
David Lang