All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Willy Tarreau <willy@w.ods.org>
Cc: 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: 23 May 2003 19:29:53 -0400	[thread overview]
Message-ID: <1053732598.1951.13.camel@mulgrave> (raw)

    although I respect your maintainer's responsible and safe position, I'd like
    to state that version 6.2.28 has been in the latest pre-releases for quite some
    time, and the reason you invoked for removing it at -rc time was the lockups
    people still encounter with the version present in -rc3, perhaps to a lesser
    extent. These lockups *SEEM* to have vanished from 6.2.33 for people who
    complained previously. Moreover, the lockup I encountered on my systems was
    fixed and demonstrated by Justin to really be a locking bug, so this was not
    just a "let's see how it behaves" fix.
    
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.

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.

In these circumstances, absent a simple fix for the problem, the only
choice seems to be reversion and trying to get the code base stable at
the beginning of the next -pre, which is the current decision.

James



             reply	other threads:[~2003-05-23 23:17 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-23 23:29 James Bottomley [this message]
2003-05-24  6:43 ` Aix7xxx unstable in 2.4.21-rc2? (RE: Linux 2.4.21-rc2) Willy Tarreau
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=1053732598.1951.13.camel@mulgrave \
    --to=james.bottomley@steeleye.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.