From: Thomas Gleixner <tglx@linutronix.de>
To: Sean <seanlkml@sympatico.ca>
Cc: Junio C Hamano <junkio@cox.net>, "H. Peter Anvin" <hpa@zytor.com>,
git@vger.kernel.org
Subject: Re: [PATCH] [RFD] Add repoid identifier to commit
Date: Thu, 12 May 2005 23:21:12 +0200 [thread overview]
Message-ID: <1115932872.11872.86.camel@tglx> (raw)
In-Reply-To: <4776.10.10.10.24.1115932163.squirrel@linux1>
On Thu, 2005-05-12 at 17:09 -0400, Sean wrote:
> On Thu, May 12, 2005 4:47 pm, Thomas Gleixner said:
>
> > As I said before timestamps can be a horrid source of information. Also
> > if you keep a list of commits merges and head forwards in timed order it
> > is simple to read the repository history, but in case of corruption you
> > have to reconstruct it manually. There is no way to do so with the
> > information available.
> >
> > Repository id's can be lost, but are simple to replace as they are
> > recorded in the commit blob.
>
> And the time is recorded on the commit blob too.
How do you enforce correct timestamps ?
tglx
Received: from simmts5-srv.bellnexxia.net (simmts5.bellnexxia.net
[206.47.199.163]) by mail.tglx.de (Postfix) with ESMTP id 623FE65C003
for <tglx@linutronix.de>; Thu, 12 May 2005 23:09:21 +0200 (CEST)
Received: from linux1 ([69.156.111.46]) by simmts5-srv.bellnexxia.net
(InterMail vM.5.01.06.10 201-253-122-130-110-20040306) with ESMTP id
<20050512210923.CCQN11606.simmts5-srv.bellnexxia.net@linux1>; Thu, 12
May 2005 17:09:23 -0400
next prev parent reply other threads:[~2005-05-12 21:13 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-11 21:38 [PATCH] [RFD] Add repoid identifier to commit Thomas Gleixner
2005-05-11 22:00 ` Sean
2005-05-11 22:05 ` Thomas Gleixner
2005-05-11 22:24 ` Sean
2005-05-11 22:30 ` Thomas Gleixner
2005-05-11 22:36 ` Sean
2005-05-11 22:48 ` Thomas Gleixner
2005-05-11 23:01 ` Sean
2005-05-11 23:33 ` Thomas Gleixner
2005-05-11 23:44 ` Sean
2005-05-12 0:30 ` Thomas Gleixner
2005-05-12 0:45 ` Sean
2005-05-12 0:56 ` Thomas Gleixner
2005-05-12 0:58 ` Sean
2005-05-12 10:07 ` David Woodhouse
2005-05-12 10:18 ` Sean
2005-05-12 10:42 ` Thomas Gleixner
2005-05-12 10:43 ` David Woodhouse
2005-05-12 10:58 ` Sean
2005-05-12 10:39 ` Sean
2005-05-11 23:14 ` H. Peter Anvin
2005-05-11 23:38 ` Thomas Gleixner
2005-05-11 23:40 ` H. Peter Anvin
2005-05-11 23:45 ` Sean
2005-05-12 0:04 ` H. Peter Anvin
2005-05-12 0:20 ` Sean
2005-05-12 0:33 ` Thomas Gleixner
2005-05-12 1:46 ` Junio C Hamano
2005-05-12 7:57 ` Thomas Gleixner
2005-05-12 9:32 ` Sean
2005-05-12 9:39 ` Thomas Gleixner
2005-05-12 9:46 ` Sean
2005-05-12 11:18 ` Thomas Gleixner
2005-05-12 11:24 ` Sean
2005-05-12 11:43 ` Thomas Gleixner
2005-05-12 11:48 ` Sean
2005-05-12 12:16 ` Thomas Gleixner
2005-05-12 12:16 ` Sean
2005-05-12 12:34 ` Thomas Gleixner
2005-05-12 12:35 ` Sean
2005-05-12 12:17 ` Sean
2005-05-12 12:29 ` David Woodhouse
2005-05-12 12:32 ` Sean
2005-05-12 13:29 ` Jan Harkes
2005-05-12 15:44 ` Jon Seymour
2005-05-12 15:48 ` Jon Seymour
2005-05-12 15:50 ` Jon Seymour
2005-05-12 16:20 ` Jan Harkes
2005-05-12 17:09 ` Jon Seymour
2005-05-12 17:12 ` Jon Seymour
2005-05-12 17:35 ` Junio C Hamano
2005-05-12 18:18 ` Sean
2005-05-12 19:24 ` Junio C Hamano
2005-05-12 19:35 ` Sean
2005-05-12 20:47 ` Thomas Gleixner
2005-05-12 21:09 ` Sean
2005-05-12 21:21 ` Thomas Gleixner [this message]
2005-05-12 21:32 ` Sean
2005-05-12 21:44 ` Junio C Hamano
2005-05-12 22:06 ` Thomas Gleixner
2005-05-12 22:24 ` Sean
2005-05-12 0:41 ` Dmitry Torokhov
2005-05-12 0:44 ` Thomas Gleixner
2005-05-12 1:09 ` H. Peter Anvin
2005-05-12 1:13 ` H. Peter Anvin
2005-05-12 3:30 ` Joel Becker
2005-05-12 9:17 ` Thomas Gleixner
2005-05-13 1:37 ` [PATCH] [RFD] Add repoid identifier to commit [its a workspace id, isn't it?] Jon Seymour
2005-05-13 8:36 ` Thomas Gleixner
2005-05-13 22:25 ` Petr Baudis
2005-05-13 22:26 ` H. Peter Anvin
2005-05-13 23:39 ` Petr Baudis
2005-05-13 23:49 ` Jon Seymour
2005-05-14 5:02 ` Jon Seymour
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=1115932872.11872.86.camel@tglx \
--to=tglx@linutronix.de \
--cc=git@vger.kernel.org \
--cc=hpa@zytor.com \
--cc=junkio@cox.net \
--cc=seanlkml@sympatico.ca \
/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.