From: Nicolas Pitre <nico@cam.org>
To: lkml <linux-kernel@vger.kernel.org>
Cc: Jon Smirl <jonsmirl@gmail.com>, Git Mailing List <git@vger.kernel.org>
Subject: Git tree for old kernels
Date: Sun, 19 Aug 2007 15:24:56 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.0.999.0708191453030.16727@xanadu.home> (raw)
In-Reply-To: <9e4733910707221349s462aa11bj714956f7cdc72aac@mail.gmail.com>
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
It currently stops at Linux v1.0. I would like to continue populating
this archive up to the current "Linux kernel history" Git repository
from Thomas Gleixner which currently doesn't go further back than
v2.4.0. This is however extremely time consuming to track down old
mailing list and newsgroup archives in order to find announcements to
serve as commit log material. Therefore I'd be really glad if people
could help me find those and send me copies of relevant announcements.
The content of the current archive should give a good idea of what I'm
looking for.
Also, the following items are currently missing and apparently vanished
from the surface of the planet:
- v0.02 sources
- v0.03 sources and announcement
- v0.10 announcement
- v0.96 sources
- sources for v0.99.13{abcdefghij} (got k, don't know where the serie
ends) as well as announcements for all of them
- all announcements for v0.99.14{a-z} except for pl14r
- announcements for pl15c to pl15j, 1.0-pre1, and ALPHA-1.0.
If you happen to have any of those please drop me a note.
Otherwise the archive appears fairly complete with almost 3 years of
Linux development history captured in a 3MB pack file.
Nicolas
next prev parent reply other threads:[~2007-08-19 19:25 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 ` Nicolas Pitre [this message]
2007-08-20 17:16 ` Git tree for old kernels Josef Sipek
2007-08-20 17:40 ` Nicolas Pitre
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.0708191453030.16727@xanadu.home \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=jonsmirl@gmail.com \
--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).