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 09:55:24 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	"H. Peter Anvin" <hpa@...or.com>
cc:	Jan Engelhardt <jengelh@...putergmbh.de>,
	Paul Mundt <lethal@...ux-sh.org>,
	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, 22 Jul 2007, H. Peter Anvin wrote:
> 
> Wouldn't be hard to make a git tree with all the patches all the way
> back to 0.01 even...

I actually tried to get something like this together back in the BK days 
and early in the SCO saga. It was pretty painful to try to find all the 
historic trees and patches - they're all in different format, and some of 
them are unreliable (ie CVS imports by people like Ted).

The good news is that git would be a lot more natural to the process of 
trying to create a history, because you could basically import random 
trees, and tag them as just independent trees, and then re-create the 
history after-the-fact by trying to stitch them all together. And if you 
find a new tree, you'd just re-stitch it - something that was very hard to 
do with BK (and BK generally wouldn't help you with keeping multiple 
independent trees around, and wouldn't generally accept the notion of 
re-doing the histories and keeping various versions of the histories 
around).

So I've been thinking about trying to re-create some really old history 
into git, but it's still a lot of work.. And obviously not very useful, 
just interesting from an archeological standpoint.

			Linus
-
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/