linux-kernel - Re: Git tree for old kernels from before the current tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 23 Jul 2007 06:13:14 +0900
From:	Paul Mundt <lethal@...ux-sh.org>
To:	Jan Engelhardt <jengelh@...putergmbh.de>
Cc:	Jon Smirl <jonsmirl@...il.com>,
	Git Mailing List <git@...r.kernel.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: Git tree for old kernels from before the current tree

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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/