From: Jeff Garzik <jgarzik@pobox.com>
To: bill davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: libata in 2.4.24?
Date: Tue, 02 Dec 2003 17:34:48 -0500 [thread overview]
Message-ID: <3FCD1388.2020907@pobox.com> (raw)
In-Reply-To: <bqj2al$dmc$1@gatekeeper.tmr.com>
bill davidsen wrote:
> Unless a miracle occurs it will take as long for 2.6 to be really stable
> and fully functional as it did for 2.[024]. When it goes out in distros
> and gets abused by users for a while the sharp corners will be broken off.
I think that's a bit of an extremist view.
The 2.6 rpms Arjan has posted have gotten good use, and most people seem
to think 2.6.0-test is a _lot_ more stable than 2.4.0 was at release time.
It's certainly true that a raft of currently-unknown bugs will show up
when distros start shipping 2.6-based distros (I think the first was
Mandrake, as an experimental extra, soon be followed by Fedora?). Such
bugs always appear.
I venture to say, for the vast majority of hardware, including my 28MB
K6-2 laptop and my P133 firewall, 2.6 works just as well as 2.4 does
currently.
Jeff
next prev parent reply other threads:[~2003-12-02 22:35 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-01 13:41 libata in 2.4.24? Xose Vazquez Perez
2003-12-01 14:11 ` Marcelo Tosatti
2003-12-02 19:59 ` Stephan von Krawczynski
2003-12-02 22:05 ` bill davidsen
2003-12-02 22:34 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-03 0:34 Xose Vazquez Perez
2003-11-28 18:27 linux-2.4.23 released Marcelo Tosatti
2003-11-29 22:26 ` libata in 2.4.24? Samuel Flory
2003-11-29 23:10 ` Marcelo Tosatti
2003-12-01 10:43 ` Marcelo Tosatti
2003-12-01 18:06 ` Samuel Flory
2003-12-01 21:12 ` Greg Stark
2003-12-01 21:23 ` Samuel Flory
2003-12-01 21:44 ` Greg Stark
2003-12-01 22:00 ` Jeff Garzik
2003-12-01 22:06 ` Samuel Flory
2003-12-01 22:00 ` Erik Steffl
2003-12-02 5:36 ` Greg Stark
[not found] ` <20031202055336.GO1566@mis-mike-wstn.matchmail.com>
2003-12-02 5:58 ` Mike Fedyk
2003-12-02 16:31 ` Greg Stark
2003-12-02 17:40 ` Mike Fedyk
2003-12-02 18:04 ` Jeff Garzik
2003-12-02 18:46 ` Mike Fedyk
2003-12-02 18:49 ` Jeff Garzik
2003-12-04 8:18 ` Jens Axboe
2003-12-02 18:02 ` Jeff Garzik
2003-12-02 18:51 ` Greg Stark
2003-12-02 19:06 ` Jeff Garzik
2003-12-02 20:10 ` Greg Stark
2003-12-02 20:16 ` Jeff Garzik
2003-12-02 20:34 ` Greg Stark
2003-12-02 22:34 ` bill davidsen
2003-12-02 23:02 ` Mike Fedyk
2003-12-02 23:18 ` bill davidsen
2003-12-02 23:40 ` Mike Fedyk
2003-12-03 0:01 ` Jeff Garzik
2003-12-03 0:47 ` Jamie Lokier
2003-12-07 5:33 ` Bill Davidsen
2003-12-01 21:36 ` Justin Cormack
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=3FCD1388.2020907@pobox.com \
--to=jgarzik@pobox.com \
--cc=davidsen@tmr.com \
--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.