git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Git tree for old kernels from before the current tree
Date: Sun, 22 Jul 2007 16:49:48 -0400	[thread overview]
Message-ID: <9e4733910707221349s462aa11bj714956f7cdc72aac@mail.gmail.com> (raw)

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? No history in the
tree, just a simple way to quickly fetch and select a copy of all the
various old releases. I know they are all available ftp, git tree
would organize them all in one place and let you fetch them all at
once.

If this is small enough you could add it to the current kernel tree.
Git's super diffing performance might make this fairly small.

My dream system lets me checkout an ancient version, apply the diff
from the vendor (or expand a tarball), use git status to see what
files changed, and git diff to get detailed changes (all minus CVS
keyword expansion noise). Major bonus points if it can detect detect a
subsystem that has been backported.

-- 
Jon Smirl
jonsmirl@gmail.com

             reply	other threads:[~2007-07-22 20:49 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-22 20:49 Jon Smirl [this message]
2007-07-22 21:00 ` Git tree for old kernels from before the current tree 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 ` 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=9e4733910707221349s462aa11bj714956f7cdc72aac@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).