From: Chris Snook <csnook@redhat.com>
To: ciol <ciol13@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [poll] Is the megafreeze development model broken?
Date: Thu, 08 Nov 2007 19:15:34 -0500 [thread overview]
Message-ID: <4733A6A6.5000605@redhat.com> (raw)
In-Reply-To: <fgvs7p$j0d$1@ger.gmane.org>
ciol wrote:
> Chris Snook wrote:
>
>> Why are you asking the developers? We do this for the sake of the users.
>
>
> The kernel is the software of the developers.
The kernel is a technology. A distribution is a product. When decisions about
technology and decisions about products are made *entirely* by the same people,
the result is never good.
> It's important to know how they want it to be distributed.
For commercial distributions, the answer is: "In whichever way results in the
largest paycheck with the least amount of stress and effort", which means doing
it the way that's best for the customer.
Non-commercial distributions have less of this pressure, but the same principle
applies if they care about their users. If you're not interested in the users
but you are interested in the technology, you should be doing your work
upstream, so the distribution is irrelevant.
Don't get me wrong, I think stable kernel trees like 2.6.16 are a good thing.
They serve very well a whole bunch of different niches where users are willing
to sacrifice the support benefits of a distribution kernel for the control of an
upstream kernel, while maintaining the stability of their installed base. These
users have little interest in the general-purpose distribution kernel anyway,
aside from perhaps wishing it included some config or patch that its maintainers
have elected not to include.
-- Chris
next prev parent reply other threads:[~2007-11-09 1:30 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 22:56 [poll] Is the megafreeze development model broken? ciol
2007-11-07 23:06 ` Rik van Riel
2007-11-07 23:11 ` ciol
2007-11-08 1:36 ` Adrian Bunk
2007-11-08 20:45 ` ciol
2007-11-08 6:18 ` Stephen Hemminger
2007-11-08 13:38 ` David Newall
2007-11-08 14:26 ` Chris Snook
2007-11-08 20:41 ` ciol
2007-11-09 0:15 ` Chris Snook [this message]
2007-11-12 11:09 ` Eric W. Biederman
2007-11-12 13:51 ` Tuomo Valkonen
2007-11-12 15:20 ` Adrian Bunk
2007-11-12 16:02 ` Tuomo Valkonen
2007-11-12 16:56 ` Adrian Bunk
2007-11-12 17:16 ` Tuomo Valkonen
2007-11-12 17:34 ` Adrian Bunk
2007-11-12 17:42 ` Tuomo Valkonen
2007-11-13 10:11 ` David Newall
2007-11-12 17:37 ` Rogelio M. Serrano Jr.
2007-11-12 17:53 ` Tuomo Valkonen
2007-11-13 12:28 ` Radoslaw Szkodzinski
2007-11-13 13:09 ` Tuomo Valkonen
2007-11-12 16:13 ` Rogelio M. Serrano Jr.
2007-11-12 17:14 ` Adrian Bunk
2007-11-12 17:18 ` Tuomo Valkonen
2007-11-12 23:39 ` Matthias Schniedermeyer
2007-11-13 0:12 ` Tuomo Valkonen
2007-11-12 17:30 ` david
2007-11-12 18:25 ` Rogelio M. Serrano Jr.
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=4733A6A6.5000605@redhat.com \
--to=csnook@redhat.com \
--cc=ciol13@gmail.com \
--cc=linux-kernel@vger.kernel.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