From: Bill Davidsen <davidsen@tmr.com>
To: grouch@edge-op.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel releases 0.01 - 2.6.2
Date: Fri, 06 Feb 2004 13:22:03 -0500 [thread overview]
Message-ID: <4023DB4B.3060008@tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.51.0402041746050.19792@jak.edge-op.org>
grouch@edge-op.org wrote:
> At the suggestion of a subscriber to this list,
> and before the 10th anniversary of Linux v1.0:
>
> Dates and versions of kernel releases, 0.01 to 2.6.2
>
> http://edge-op.org/files/kernel-releases.html (table)
> http://edge-op.org/files/kernel-releases (plain text)
>
> (You folks have cranked out an amazing amount!)
Thanks for the timeline, may it continue! I can't believe how long I
have run machines once they became stable... my last 1.2.13 machine was
taken down on Y2k-eve, I still have a 2.1.106 machine running, and a
2.0.33 machine was upgraded to RHEL-3.0 early this year. Speaks well for
stability that machines without security issues can just run virtually
forever.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
prev parent reply other threads:[~2004-02-06 18:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 23:53 Kernel releases 0.01 - 2.6.2 grouch
2004-02-06 18:22 ` Bill Davidsen [this message]
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=4023DB4B.3060008@tmr.com \
--to=davidsen@tmr.com \
--cc=grouch@edge-op.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.