From: Willy Tarreau <willy@w.ods.org>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: Willy Tarreau <willy@w.ods.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
gibbs@scsiguy.com
Subject: Re: Aix7xxx unstable in 2.4.21-rc2? (RE: Linux 2.4.21-rc2)
Date: Sat, 24 May 2003 08:43:40 +0200 [thread overview]
Message-ID: <20030524064340.GA1451@alpha.home.local> (raw)
In-Reply-To: <1053732598.1951.13.camel@mulgrave>
On Fri, May 23, 2003 at 07:29:53PM -0400, James Bottomley wrote:
> I think there's some misunderstanding about what a release candidate
> is. It's an attempt to see if a particular set of code is viable as the
> released product. Any bugs reported against a rc that are deemed
> problems to the release need to be fixed, either by adding a simple and
> easily verifiable bug fix or by reverting the problem code.
That's also my point. People were reporting problems till -rc1 which included
driver version 6.2.28. So Marcelo reverted to 6.2.8 for -rc2 (74500 lines of
code reverted, not including doc nor aic79xx which was kept). Then, people were
still reporting problems with -rc2 which they claim are fixed by updating
to last driver updates, which were 16000 lines forward from -rc1, so less than
one fourth of what Marcelo accepted to change from -rc1 to -rc2. Although I
find this big, it's less than the change in fusion/mpt* that has gone from
-rc2 to -rc3. So I think it's not a matter of size here.
> The bksend file on http://people.freebsd.org/~gibbs/linux/SRC/
> representing the requested updates is 475k compressed. There's no
> definition of the phrase "simple and easily verifiable bug fix" I can
> encompass that could be applied to a chunk of code that size.
Most of this is a 1 MB Changelog, files going back to their original place
(Marcelo moved aic79xx to a proper directory to keep it), documentation, and
initialization code which was exploded in more little functions, then bug fixes.
I wish Justin would have proposed a little patch to fix only the locking bugs
in -rc1, but honnestly, why should he fix only these bugs when he knows about
others that must be fixed too ? I can understand he gives up. -rc is for bug
fixes, and his bug fixes are reverted !
As I said, I really hope that we'll have a quick 2.4.22 with bug fixes taken
as a priority. The current pre-releases are as frequent and as big as what
used to be full releases in the past.
Regards,
Willy
next prev parent reply other threads:[~2003-05-24 6:30 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 [this message]
2003-05-24 14:36 ` James Bottomley
2003-05-24 14:51 ` Justin T. Gibbs
2003-05-24 15:55 ` James Bottomley
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=20030524064340.GA1451@alpha.home.local \
--to=willy@w.ods.org \
--cc=James.Bottomley@steeleye.com \
--cc=gibbs@scsiguy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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