public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Ducrot Bruno <poup@poupinou.org>
Cc: Dave Jones <davej@codemonkey.org.uk>,
	Margit Schubert-While <margit@margit.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.20 ACPI
Date: Tue, 19 Nov 2002 17:45:50 +0100	[thread overview]
Message-ID: <20021119164550.GQ11952@fs.tum.de> (raw)
In-Reply-To: <20021119142731.GF27595@poup.poupinou.org>

On Tue, Nov 19, 2002 at 03:27:31PM +0100, Ducrot Bruno wrote:

>...
> I disagree with you.  It introduces more enhancements,
> and more bugfix than the current code.  I admit that tt
> could introduce some news bugs, but in the balance it
> should be more stable than before.
>...

It's not "in the balance". 2.4 is a stable kernel series. The problem is
that if you switch from one stable kernel series to another
(e.g. 2.2 -> 2.4) on a production machine you know that you have to
check whether everything works as before you upgrade your production
machines. This can take quite some time. Within a stable kernel series
everything that worked in earlier kernels within this series should work
in future kernels in this kernel series. Don't forget that e.g. a
fixed security problem might force people to do a quick upgrade of
production machines to the latest kernel in this series.

There's always the possibility that you apply patches or use one of the
many two-to-four-letter patches which might contain the patch you
need.

Note: I don't know the specific situation with the new ACPI code and
      whether it might be good to include it, my arguments are an
      answer to your "in the balance" argument.

> Cheers,

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2002-11-19 16:38 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-19 12:53 Linux 2.4.20 ACPI Margit Schubert-While
2002-11-19 13:07 ` Dave Jones
2002-11-19 14:27   ` Ducrot Bruno
2002-11-19 16:45     ` Adrian Bunk [this message]
2002-11-23 19:57       ` Pavel Machek
2002-11-25 12:15         ` Dave Jones
2002-11-25 12:37           ` Arjan van de Ven
2002-11-25 16:07           ` David Woodhouse
2002-11-25 16:33             ` John Jasen
2002-11-25 18:12             ` Pavel Machek
2002-11-25 21:34               ` David Woodhouse
2002-11-25 22:26                 ` Alan Cox
2002-11-25 23:53                 ` Tom Diehl
2002-11-19 17:29     ` Dave Jones
2002-11-19 18:30     ` Dave Jones
2002-11-20  6:37       ` Ducrot Bruno
2002-11-20 10:29         ` Felix Seeger
2002-11-20 15:11           ` Ducrot Bruno
  -- strict thread matches above, loose matches on Subject: below --
2002-11-20 11:02 Margit Schubert-While
2002-11-20 20:00 ` Willy Tarreau
2002-11-20 19:08 Grover, Andrew
2002-11-20 21:47 ` David Woodhouse
2002-11-20 22:24   ` Alan Cox
2002-11-20 21:59     ` David Woodhouse
2002-11-20 22:34       ` Alan Cox
2002-11-21 13:11       ` Ducrot Bruno
2002-11-21  1:24 Grover, Andrew
2002-11-21  1:45 ` Dave Jones
2002-11-26 11:09 Margit Schubert-While
     [not found] <r1_Pine.LNX.4.44.0211251848000.8602-100000@tigger.rogueind.com>
2002-11-27 19:09 ` Bill Davidsen

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=20021119164550.GQ11952@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=margit@margit.com \
    --cc=poup@poupinou.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