git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Pitre <nico@cam.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	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 16:45:10 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.0.999.0707231638330.6355@xanadu.home> (raw)
In-Reply-To: <alpine.LFD.0.999.0707231250390.3607@woody.linux-foundation.org>

On Mon, 23 Jul 2007, Linus Torvalds wrote:

> 
> 
> On Mon, 23 Jul 2007, Nicolas Pitre wrote:
> > 
> > What is missing is:
> > 
> >  - v0.02 sources
> 
> I think this really is gone. 0.03 was such an improvement on 0.02 that I 
> think what happened was that I literally removed 0.02 (hey, it wasn't 
> historically interesting at the time!). It's not the first time people 
> have wondered about it.
> 
> 0.03 was the first version where you could actually do things under Linux, 
> and I think I could compile etc. I *think* it was released pretty close 
> after 0.02, which made 0.02 appear even more flawed and a brown-paper-bag 
> release.

Could that version be found anywhere?

> >  - v0.10 announcement
> 
> Hmm. That one would be interesting, since the reason for the 0.03->0.10 
> jump was that I was getting so happy with how it was actually working for 
> me (ie able to compile itself under itself). But I don't see it, and it's 
> not on google in the comp.os.minix archives either, afaik.

Anyone out there keeping an archive of those old posts?  Archival sites 
appear to have a black hole during that period.

> >  - v0.99.12 announcement
> 
> Well, the 0.99.12 announcement is found by google.
> 
> 	http://groups.google.com/group/comp.os.linux.announce/browse_thread/thread/8a19289f68a4af35/fe433c9df4b382a5?lnk=st&q=&rnum=1#fe433c9df4b382a5
> 
> In general, google groups (search by date and author, and make the group 
> be something like *linux*) is good, I found the above on the first try.

Yeah... Don't know what happened.  I must have found it then because I 
had a file to store it in my data directory, but somehow it was empty.  
Fixed now.


Nicolas

  reply	other threads:[~2007-07-23 20:45 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 [this message]
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.0707231638330.6355@xanadu.home \
    --to=nico@cam.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 \
    --cc=torvalds@linux-foundation.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).