From: Paul Mundt <lethal@linux-sh.org>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Jon Smirl <jonsmirl@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Git tree for old kernels from before the current tree
Date: Mon, 23 Jul 2007 06:13:14 +0900 [thread overview]
Message-ID: <20070722211314.GA13850@linux-sh.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0707222257540.32367@fbirervta.pbzchgretzou.qr>
On Sun, Jul 22, 2007 at 11:00:15PM +0200, Jan Engelhardt wrote:
> On Jul 22 2007 16:49, 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?
>
> Well, it would be cool if history was somehow available (I recognize
> this would be a lot of work). One currently has to go through the
> bk repo if something is to be searched for in that timeframe.
>
Err, that's crap. Have you even looked at gitweb? There's at least:
git://git.kernel.org/pub/scm/linux/kernel/git/tglx/history.git
This has trees all the way back to 2.5.0.
and Linus also has:
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/old-2.6-bkcvs.git
for the BK history.
That's already more history than most people have any immediate use for,
going beyond that starts getting in to general completeness before
practical application territory.
Anyone still sending 2.4 patches with the intent of them being moved
forward and applied to a current kernel needs to be killfiled.
next prev parent reply other threads:[~2007-07-22 21:13 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 [this message]
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
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=20070722211314.GA13850@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=git@vger.kernel.org \
--cc=jengelh@computergmbh.de \
--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).