From: Linus Torvalds <torvalds@linux-foundation.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
Paul Mundt <lethal@linux-sh.org>, 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 09:55:24 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.999.0707230950340.3607@woody.linux-foundation.org> (raw)
In-Reply-To: <46A3D5EA.2050600@zytor.com>
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
next prev parent reply other threads:[~2007-07-23 16:55 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-22 20:49 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 [this message]
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=alpine.LFD.0.999.0707230950340.3607@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=hpa@zytor.com \
--cc=jengelh@computergmbh.de \
--cc=jonsmirl@gmail.com \
--cc=lethal@linux-sh.org \
--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
all inboxes | Powered by JetHome®