From: James Bottomley <James.Bottomley@steeleye.com>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: Willy Tarreau <willy@w.ods.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: Aix7xxx unstable in 2.4.21-rc2? (RE: Linux 2.4.21-rc2)
Date: 24 May 2003 11:55:54 -0400 [thread overview]
Message-ID: <1053791756.1793.55.camel@mulgrave> (raw)
In-Reply-To: <156240000.1053787871@aslan.scsiguy.com>
On Sat, 2003-05-24 at 10:51, Justin T. Gibbs wrote:
> Just for clarification. Marcelo never asked me for a fix. The only
> mail I received from him was an informational message indicating that
> the code was being backed out. If I had been provided an opportunity
> to fix the problem, I would have. Considering that the fix has been
> available long before RC2 was cut (May 1st.), it's not hard to see that
> getting a proper fix required nothing more than just upgrading the driver
> or contacting its maintainer to get a paired down fix.
The kernel, as you have been told several times before, follows a push
model, not a pull one. Just looking after SCSI, I don't have time to go
around asking all the driver writers for updates; likewise Marcelo
really doesn't have the time to do this for everything in the 2.4
kernel.
Every maintained piece of the kernel has a listed maintainer to whom the
bug reports are supposed to go. The expectation is that these
maintainers will see the bug reports and pro-actively provide fixes
before they become release issues. The maintainers also do
enhancements, *but* these enhancements should follow the proper release
cycle (i.e. in at the early -pre stage).
Could you please get with the program? The bug fix vs enhancement issue
hasn't previously mattered that much for 2.5, but I anticipate we'll be
following a similar model when 2.6 is released.
James
next prev parent reply other threads:[~2003-05-24 15:43 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 23:29 Aix7xxx unstable in 2.4.21-rc2? (RE: Linux 2.4.21-rc2) James Bottomley
2003-05-24 6:43 ` Willy Tarreau
2003-05-24 14:36 ` James Bottomley
2003-05-24 14:51 ` Justin T. Gibbs
2003-05-24 15:55 ` James Bottomley [this message]
2003-05-28 23:08 ` Bill Davidsen
2003-05-26 4:21 ` David S. Miller
2003-05-26 4:25 ` David S. Miller
2003-05-26 8:47 ` Marc-Christian Petersen
2003-05-26 17:58 ` Marcelo Tosatti
2003-05-26 22:44 ` Aix7xxx unstable in 2.4.21-rc2? David S. Miller
2003-05-26 18:42 ` Aix7xxx unstable in 2.4.21-rc2? (RE: Linux 2.4.21-rc2) Marcelo Tosatti
2003-05-26 21:29 ` Willy Tarreau
2003-05-26 21:35 ` Marcelo Tosatti
2003-05-27 4:21 ` Willy Tarreau
2003-05-26 22:16 ` Carl-Daniel Hailfinger
2003-05-26 22:18 ` Marc-Christian Petersen
2003-05-26 22:33 ` Carl-Daniel Hailfinger
2003-05-27 0:35 ` Alan Cox
2003-05-27 4:39 ` Willy Tarreau
2003-05-27 4:47 ` Marcelo Tosatti
2003-05-27 5:00 ` Willy Tarreau
2003-05-27 8:38 ` Oliver Pitzeier
2003-05-27 8:44 ` Marc-Christian Petersen
2003-05-27 9:44 ` Oliver Pitzeier
2003-05-27 20:01 ` Marcelo Tosatti
2003-06-23 7:57 ` Oliver Pitzeier
-- strict thread matches above, loose matches on Subject: below --
2003-05-27 9:12 Eric Valette
2003-05-26 21:53 john
[not found] <20030523085010$1ac2@gated-at.bofh.it>
[not found] ` <20030523180021$109a@gated-at.bofh.it>
[not found] ` <20030523203017$0e66@gated-at.bofh.it>
2003-05-24 11:46 ` Pascal Schmidt
2003-05-24 20:06 ` Nicholas Wourms
2003-05-28 23:11 ` Bill Davidsen
2003-05-11 19:08 Linux 2.4.21-rc2 Sven Krohlas
2003-05-22 15:19 ` Aix7xxx unstable in 2.4.21-rc2? (RE: Linux 2.4.21-rc2) Oliver Pitzeier
2003-05-22 15:31 ` Marc-Christian Petersen
2003-05-22 21:33 ` Scott McDermott
2003-05-23 8:45 ` Oliver Pitzeier
2003-05-23 17:52 ` Marcelo Tosatti
2003-05-23 20:19 ` Willy Tarreau
2003-05-23 22:58 ` Scott McDermott
2003-05-26 18:51 ` Marcelo Tosatti
2003-05-23 7:17 ` Sven Krohlas
2003-05-26 12:54 ` Matthias Andree
2003-05-23 7:14 ` Sven Krohlas
2003-05-23 8:48 ` Oliver Pitzeier
2003-05-23 9:26 ` Sven Krohlas
2003-05-23 9:32 ` Oliver Pitzeier
2003-05-23 11:33 ` Stephan von Krawczynski
2003-05-24 0:18 ` J.A. Magallon
2003-05-23 15:20 ` Disconnect
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=1053791756.1793.55.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=gibbs@scsiguy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=willy@w.ods.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.