Stephan von Krawczynski wrote:
> On Wed, 11 Jun 2003 23:15:06 +0200
> Adrian Bunk <email@example.com> wrote:
>>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.
> You cannot fulfill that in reality. Looking at the broad variety of software
> out there you simply cannot know all the implications a simple bug fix may
> have. There may well be boxes that rely on a broken code you just fixed. Only
> god knows. So you sometimes simply have to do "the right thing"(tm) knowing
> there will always be people who shoot you for it.
Just to go a little bit more in that direction, I already have seen an
obvious one-line patch that caused a deadlock in another OS because due
to code location change and probably an additionnal cache miss on
specific part of the code, an existing synchronisation bug that was
never triggered started to effectively happen...
Besides, if you please 1000 users and cause problem to 2 of them because
they have broken hardware, I think you are going into the right direction.
>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)
Bug fixes are meant to make the 2.4 kernel more useable right? So I do
not reallly see the utimate difference with other things in your
category. What I was asking is a rationnal way of chosing the
priorities. You gave me yours without real explanation.
The purpose of the original mail was to ask for discussion/clarification
on 2.4 development priorities (e.g something like the 2.6 todo list) and
a proposal to set up the priorities using generic targetted hardware
(server, laptop, desktop) as hint for requirement selection.
-- __ / ` 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: firstname.lastname@example.org
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Jun 15 2003 - 22:00:32 EST