git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Pitre <nico@cam.org>
To: Josef Sipek <jsipek@fsl.cs.sunysb.edu>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Jon Smirl <jonsmirl@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: Git tree for old kernels
Date: Mon, 20 Aug 2007 13:40:52 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.0.999.0708201334000.16727@xanadu.home> (raw)
In-Reply-To: <20070820171618.GB9869@filer.fsl.cs.sunysb.edu>

On Mon, 20 Aug 2007, Josef Sipek wrote:

> On Sun, Aug 19, 2007 at 03:24:56PM -0400, Nicolas Pitre wrote:
> > On Sun, 22 Jul 2007, Jon Smirl wrote:
> > 
> > > Continuing on with kernel archeology for embedded systems, any
> > > interest in making a git tree with all of the kernel versions from the
> > > beginning up to the start of the current git tree?
> > 
> > I just put the archive I've gathered so far in a Git tree on kernel.org:
> > 
> >     git://git.kernel.org/pub/scm/linux/kernel/git/nico/archive.git
> > 
> > It is also available through gitweb from:
> > 
> >     http://git.kernel.org/?p=linux/kernel/git/nico/archive.git
>  
> I don't mean to nit-pick but, would it be possible to have the timestamps
> for the commits closer to the release dates?

Well, the author timestamp already is, based on the date of the 
announcement message used for the commit log, including the timezone.  
If you find errors in those please tell me.

The commit timestamp, however, is the time when _I_ created the 
repository, hence it should not be that interesting.

> I must say, impressive work.

Thanks!


Nicolas

  reply	other threads:[~2007-08-20 17:41 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-22 20:49 Git tree for old kernels from before the current tree Jon Smirl
2007-07-22 21:00 ` Jan Engelhardt
2007-07-22 21:13   ` Paul Mundt
2007-07-22 21:46     ` Jan Engelhardt
2007-07-22 22:00       ` Jan Engelhardt
2007-07-22 22:10         ` H. Peter Anvin
2007-07-22 23:26           ` Michael Tharp
2007-07-23  0:17             ` Jon Smirl
2007-07-23 16:55           ` Linus Torvalds
2007-07-23 17:48             ` Nicolas Pitre
2007-07-23 18:02               ` Linus Torvalds
2007-07-23 19:06                 ` Nicolas Pitre
2007-07-23 20:10                   ` Linus Torvalds
2007-07-23 20:45                     ` Nicolas Pitre
2007-07-23 23:11                   ` Arjan van de Ven
2007-07-23 23:46                   ` Al Viro
2007-07-23 23:49                     ` H. Peter Anvin
2007-07-24  0:10                     ` Nicolas Pitre
2007-07-24  0:12                       ` H. Peter Anvin
2007-07-24  0:36                         ` Nicolas Pitre
2007-08-20 20:09                       ` Jan-Benedict Glaw
2007-08-20 20:46                         ` Nicolas Pitre
2007-09-19  1:19                 ` Oleg Verych
2007-07-23 18:57             ` Theodore Tso
2007-07-23 19:08               ` Nicolas Pitre
2007-07-23 19:44               ` Linus Torvalds
2007-07-23 20:22                 ` Theodore Tso
2007-07-23  0:00     ` Jon Smirl
2007-08-19 19:24 ` Git tree for old kernels Nicolas Pitre
2007-08-20 17:16   ` Josef Sipek
2007-08-20 17:40     ` Nicolas Pitre [this message]
2007-08-20 18:01       ` Josef Sipek

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=alpine.LFD.0.999.0708201334000.16727@xanadu.home \
    --to=nico@cam.org \
    --cc=git@vger.kernel.org \
    --cc=jonsmirl@gmail.com \
    --cc=jsipek@fsl.cs.sunysb.edu \
    --cc=linux-kernel@vger.kernel.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).