From: Chuck Ebbert <76306.1226@compuserve.com>
To: Trent Lloyd <lathiat@bur.st>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Why no linux-2.6.8.2? (was Re: new dev model)
Date: Thu, 7 Oct 2004 03:05:38 -0400 [thread overview]
Message-ID: <200410070308_MC3-1-8BB4-FF92@compuserve.com> (raw)
Trent Lloyd wrote:
> 2.6.8.1 was released because there was a 1-line error in 2.6.8 that
> completely stopped NFS from working.
>
Yes, I know that.
> The patches mentioned below will probably go into 2.6.9 or something, if
> they have been approved for it etc.
>
A host of new bugs will probably be added too, leaving the average user with
no stable 'offical' kernel to use -- ever.
--Chuck Ebbert
Vanity kills/It don't pay bills --ABC
next reply other threads:[~2004-10-07 7:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 7:05 Chuck Ebbert [this message]
2004-10-07 7:52 ` Trent Lloyd
-- strict thread matches above, loose matches on Subject: below --
2004-10-07 16:37 Chuck Ebbert
2004-10-07 14:21 Chuck Ebbert
2004-10-07 7:05 Chuck Ebbert
2004-10-07 7:15 ` Jeff Garzik
2004-10-07 13:55 ` Alan Cox
2004-10-07 5:31 Chuck Ebbert
2004-10-07 4:46 ` alan
2004-10-07 5:49 ` Jeff Garzik
2004-10-07 5:39 ` Trent Lloyd
2004-10-07 5:43 ` Jeff Garzik
2004-10-10 16:41 ` Tomasz Torcz
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=200410070308_MC3-1-8BB4-FF92@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=lathiat@bur.st \
--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
Powered by JetHome