public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Valette <eric.valette@free.fr>
To: marcelo@conectiva.com.br
Cc: linux-kernel@vger.kernel.org
Subject: RE: 2.4.22 timeline was RE: 2.4.21-rc7 ACPI broken
Date: Wed, 11 Jun 2003 01:40:54 +0200	[thread overview]
Message-ID: <3EE66C86.8090708@free.fr> (raw)

Marcelo Tosati wrote:

 >The main reason I didnt want to merge it was due to its size. Its just 
 >too big.

 >> Please stop leading me along. Will you EVER merge it?

 >Yes, I want to, and will merge it. In 2.4.23-pre.

This kind of mails and sentence makes you lost your credibility :
	1) You said that ACPI will be merged in 2.4.22-pre,
	2) For many people ACPI (and aic7xxx) is top priority for 2.4 kernel 
(see various post including alan). The reason being that most laptop are 
unusable nowadays without ACPI,
	3) You do not explicitely says what you plan for 2.4.22...

So, for stupid people like me, could you take a little time to explains 
the dummy's what are your views about what is top priority for kernel 
and for what reasons?

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

Or maybe you simply think that software engineering is a kind of black 
art that is too hard to understand for average people...


-- 
    __
   /  `                   	Eric Valette
  /--   __  o _.          	6 rue Paul Le Flem
(___, / (_(_(__         	35740 Pace

Tel: +33 (0)2 99 85 26 76	Fax: +33 (0)2 99 85 26 76
E-mail: eric.valette@free.fr


             reply	other threads:[~2003-06-10 17:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-10 23:40 Eric Valette [this message]
2003-06-11 21:15 ` 2.4.22 timeline was RE: 2.4.21-rc7 ACPI broken Adrian Bunk
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=3EE66C86.8090708@free.fr \
    --to=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