From: Jeff King <peff@peff.net>
To: "Eric S. Raymond" <esr@thyrsus.com>
Cc: Shawn Pearce <spearce@spearce.org>,
Felipe Contreras <felipe.contreras@gmail.com>,
Junio C Hamano <gitster@pobox.com>, git <git@vger.kernel.org>
Subject: Re: Millisecond precision in timestamps?
Date: Tue, 27 Nov 2012 22:30:09 -0500 [thread overview]
Message-ID: <20121128033009.GA3931@sigill.intra.peff.net> (raw)
In-Reply-To: <20121128032337.GB1669@thyrsus.com>
On Tue, Nov 27, 2012 at 10:23:37PM -0500, Eric S. Raymond wrote:
> Jeff King <peff@peff.net>:
> > But I really wonder if anybody actually cares about adding sub-second
> > timestamp support, or if it is merely "because SVN has it".
>
> There's actually one possible other reason to care. 1-second granularity
> isn't quite fine enough to guarantee that a (committer, timestamp)
> pair is a unique key. 1 microsecond granularity would be.
You can't guarantee that such a pair is unique, anyway, due to clock
skew.
A much more compelling argument to me would be that you are doing some
bidirectional magic between git and svn, and you want to make make sure
that an svn->git->svn translation will result in the exact same bytes.
Then the argument is still "because SVN has it", but at least it is "and
we interoperate with it" and not simply chasing a cool but useless
feature.
-Peff
next prev parent reply other threads:[~2012-11-28 3:30 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 20:48 Millisecond precision in timestamps? Eric S. Raymond
2012-11-27 21:41 ` Shawn Pearce
2012-11-27 22:06 ` Junio C Hamano
2012-11-27 23:04 ` Eric S. Raymond
2012-11-27 23:49 ` Shawn Pearce
2012-11-28 0:12 ` Eric S. Raymond
2012-11-28 0:22 ` David Lang
2012-11-28 0:26 ` Felipe Contreras
2012-11-28 1:07 ` Shawn Pearce
2012-11-28 1:17 ` Jeff King
2012-11-28 1:29 ` Jason Pyeron
2012-11-28 1:42 ` Felipe Contreras
2012-11-28 3:23 ` Eric S. Raymond
2012-11-28 3:30 ` Jeff King [this message]
2012-11-28 3:44 ` Felipe Contreras
2012-11-28 3:47 ` Eric S. Raymond
2012-11-28 4:07 ` Jeff King
2012-11-28 4:25 ` Eric S. Raymond
2012-11-28 7:29 ` Junio C Hamano
2012-11-28 7:58 ` Eric S. Raymond
2012-11-28 8:04 ` David Aguilar
2012-11-28 10:14 ` Andreas Ericsson
2012-12-05 23:37 ` Robin Rosenberg
2012-12-10 20:56 ` James Cloos
2012-11-28 8:19 ` Thomas Berg
2012-11-28 8:44 ` Felipe Contreras
2012-11-28 9:10 ` Thomas Berg
[not found] ` <E4C993F4-B7A4-4CB6-A9EA-BFE98BE3A381@gmail.com>
2012-11-29 6:16 ` Eric S. Raymond
2012-11-29 7:11 ` Junio C Hamano
2012-11-29 7:22 ` Felipe Contreras
2012-11-29 10:38 ` Eric S. Raymond
2012-11-29 16:42 ` Junio C Hamano
2012-11-29 19:02 ` Eric S. Raymond
2012-11-28 17:57 ` Junio C Hamano
2012-11-28 10:10 ` Andreas Ericsson
2012-11-29 19:14 ` Phil Hord
2012-11-29 20:01 ` Jeff King
2012-11-28 1:11 ` Eric S. Raymond
2012-11-28 1:36 ` Felipe Contreras
2012-11-28 2:01 ` Junio C Hamano
2012-11-27 21:44 ` Pyeron, Jason J CTR (US)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121128033009.GA3931@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=esr@thyrsus.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=spearce@spearce.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).