From: Adrian Bunk <bunk@fs.tum.de>
To: Eric Valette <eric.valette@free.fr>
Cc: marcelo@conectiva.com.br, linux-kernel@vger.kernel.org
Subject: Re: 2.4.22 timeline was RE: 2.4.21-rc7 ACPI broken
Date: Wed, 11 Jun 2003 23:15:06 +0200 [thread overview]
Message-ID: <20030611211506.GD16164@fs.tum.de> (raw)
In-Reply-To: <3EE66C86.8090708@free.fr>
On Wed, Jun 11, 2003 at 01:40:54AM +0200, Eric Valette wrote:
>...
> I would personnally suggest that you classify the things using the
> following filter :
> a) Server (SMP, SCSI, RAID, journaling filesystems, ...),
> b) laptop (ACPI, CPUFREQ, Software suspend, IDE power save,...),
> c) desktop (File system efficiency, new hardware support,...),
> d) all systems
>...
Why are journaling filesystems only for servers?
Is file system efficiency not relevant on servers?
The important sections are more likely (ordered by priority):
- bug fixes (e.g. aic7xxx)
- support for additional hardware (e.g. ACPI update)
- new features (e.g. XFS)
These groups are not mutual exclusive, e.g. the ACPI update also
includes new features.
The important thing is that this is inside a stable kernel series and an
update that makes things better for 100 people but makes things worse
for one person is IMHO bad since it's a regression for one person.
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
next prev parent reply other threads:[~2003-06-11 21:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-10 23:40 2.4.22 timeline was RE: 2.4.21-rc7 ACPI broken Eric Valette
2003-06-11 21:15 ` Adrian Bunk [this message]
2003-06-12 11:47 ` Eric Valette
2003-06-12 14:05 ` Stephan von Krawczynski
2003-06-12 16:32 ` Eric Valette
2003-06-17 23:25 ` Marcelo Tosatti
2003-06-17 23:58 ` J.A. Magallon
2003-06-18 20:27 ` Marcelo Tosatti
2003-06-18 5:15 ` Anders Karlsson
2003-06-18 16:55 ` Bill Nottingham
2003-06-18 9:04 ` Eric Valette
-- strict thread matches above, loose matches on Subject: below --
2003-06-09 23:27 Grover, Andrew
2003-06-09 22:38 Margit Schubert-While
2003-06-10 0:08 ` Marcelo Tosatti
2003-06-09 21:47 Margit Schubert-While
2003-06-09 21:21 Grover, Andrew
2003-06-09 21:24 ` Grzegorz Jaskiewicz
2003-06-09 22:03 ` Marcelo Tosatti
2003-06-10 0:44 ` Alan Cox
2003-06-10 11:05 ` Torben Mathiasen
2003-06-10 15:14 ` Stephan von Krawczynski
2003-06-09 21:07 Margit Schubert-While
2003-06-04 20:49 Grover, Andrew
2003-06-09 20:32 ` 2.4.22 timeline was " Marcelo Tosatti
2003-06-10 0:47 ` Alan Cox
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=20030611211506.GD16164@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=eric.valette@free.fr \
--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