From: David Woodhouse <dwmw2@infradead.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Linus Torvalds <torvalds@osdl.org>, Petr Baudis <pasky@ucw.cz>,
"H. Peter Anvin" <hpa@zytor.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: kernel.org now has gitweb installed
Date: Thu, 28 Apr 2005 22:23:21 +0100 [thread overview]
Message-ID: <1114723402.2734.11.camel@localhost.localdomain> (raw)
In-Reply-To: <7v1x8u7g26.fsf@assigned-by-dhcp.cox.net>
On Thu, 2005-04-28 at 14:21 -0700, Junio C Hamano wrote:
> 2. Assuming that we do want to enforce that parent fields of a
> commit object name valid commit objects, is it OK to also
> require that the commit timestamp of a child object is not in
> the future relative to any and all of its parent commit
> objects
No. Time is utterly meaningless -- it's perfectly normal for clocks to
be out of sync. We really don't want to fall into the trap of assigning
any meaning to the timestamp.
--
dwmw2
next prev parent reply other threads:[~2005-04-28 21:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 1:38 kernel.org now has gitweb installed H. Peter Anvin
2005-04-28 4:17 ` Daniel Jacobowitz
2005-04-28 7:35 ` David Woodhouse
2005-04-28 8:10 ` Petr Baudis
2005-04-28 8:29 ` David Woodhouse
2005-04-28 9:23 ` David Woodhouse
2005-04-28 18:55 ` Linus Torvalds
2005-04-28 21:20 ` David Woodhouse
2005-04-28 21:40 ` Linus Torvalds
2005-04-28 21:47 ` David Woodhouse
2005-04-28 21:50 ` H. Peter Anvin
2005-04-28 21:52 ` H. Peter Anvin
2005-04-28 22:12 ` Linus Torvalds
2005-04-28 22:12 ` David Woodhouse
2005-04-29 2:46 ` Jan Harkes
2005-04-28 21:21 ` Junio C Hamano
2005-04-28 21:23 ` David Woodhouse [this message]
2005-04-28 21:44 ` Junio C Hamano
2005-04-28 22:04 ` Linus Torvalds
2005-04-28 22:59 ` Gerhard Schrenk
2005-04-28 21:38 ` David Woodhouse
2005-04-28 21:49 ` Junio C Hamano
2005-04-28 21:44 ` Linus Torvalds
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=1114723402.2734.11.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--cc=git@vger.kernel.org \
--cc=hpa@zytor.com \
--cc=junkio@cox.net \
--cc=pasky@ucw.cz \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.