git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Nicolas Pitre <nico@cam.org>
Cc: Al Viro <viro@ftp.linux.org.uk>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	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 17:12:54 -0700	[thread overview]
Message-ID: <46A54406.8020605@zytor.com> (raw)
In-Reply-To: <alpine.LFD.0.999.0707231957450.6355@xanadu.home>

Nicolas Pitre wrote:
> 
> I have sanitized .tgz files that I use to stuff a Git repo with.  I 
> recall that some of them were reconstructed through patching an earlier 
> or later kernel version because the original ones were corrupted. Some 
> patches were retrieved from other archival sites, etc.  Then the result 
> was 
> cross checked with summary lists like this one: 
> 
> http://www.uwsg.iu.edu/hypermail/linux/kernel/0110.1/1684.html
> 
> This was a while ago so I don't remember the exact steps, but that 
> wasn't always trivial.
> 

Then there is 0.95a, 0.95c and 0.95c+, which as far as I know only ever
existed as 0.95 + patches posted to alt.os.linux.

	-hpa

  reply	other threads:[~2007-07-24  0:16 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
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 [this message]
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=46A54406.8020605@zytor.com \
    --to=hpa@zytor.com \
    --cc=git@vger.kernel.org \
    --cc=jengelh@computergmbh.de \
    --cc=jonsmirl@gmail.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico@cam.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@ftp.linux.org.uk \
    /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).