All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: A users thoughts on the new dev. model
Date: Thu, 22 Jul 2004 18:25:46 -0400	[thread overview]
Message-ID: <cdpee5$otu$1@gatekeeper.tmr.com> (raw)
In-Reply-To: <40FFD760.8060504@unix.eng.ua.edu>

Evan Hisey wrote:
> To the Dev list:
>    First, thanks for all the work on the kernel. I try to keep up with 
> the list via both KernelTrap and  Kerneltraffic. Today I just saw the 
> discussion on the new development model.  As an end use of the vanilla 
> tree, I would like to point out that a large number of people and 
> projects rely on the vanilla kernel to be the stable tree do to the 
> overly varied and random patching nature of vendor supplied kernels 
> making them hard to call reliable. In the case of my preferred distro 
> Slackware,  the distro itself expects the vanilla tree to be stable and 
> reliable enough to not need any patches.  I believe this is the case for 
> a large number off distro' s and end users. Thank you for your time. 
> Please send any flames,comments, or complaints via CC, as I am not 
> sucribed to the list.

I confess I feel that this new model is a return to the bad old days 
when the stable tree wasn't. Sounds as if Andrew is bored with the idea 
of letting 2.7 be the development tree and just being the gatekeeper of 
STABLE new features for 2.6. Perhaps 2.7 should be opened and Andrew 
will have a place to play, and features can drift to 2.6 more slowly.

I agree that vendor kernels often have unexpected behaviour, 
"improvements" on the API, etc. They sometimes protect the user from 
himself, so that code which works fine on a vendor kernel fails 
miserably on a mainline kernel.

I'm sure developers will do whatever they please, but I think a 
development kernel would be nice about now, so people could try new 
things without restriction, and people who like to use a stable kernel 
could have one.

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

  reply	other threads:[~2004-07-22 22:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-22 15:04 A users thoughts on the new dev. model Evan Hisey
2004-07-22 22:25 ` Bill Davidsen [this message]
2004-07-23 13:58   ` H. Peter Anvin
2004-07-23 15:24     ` szonyi calin
2004-07-23 16:39       ` David Ford
2004-07-23 19:06         ` Xiong Jiang
2004-07-23 20:00           ` Tim Wright
2004-07-23 21:40     ` Adrian Bunk
2004-07-23 23:04       ` hpa
2004-07-24 10:38         ` Adrian Bunk
2004-07-27 20:08       ` Bill Davidsen
2004-07-22 22:57 ` Paul Jackson
2004-07-27 20:20   ` Bill Davidsen
2004-07-28  7:31     ` Paul Jackson
2004-07-23 19:32 ` Florin Andrei

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='cdpee5$otu$1@gatekeeper.tmr.com' \
    --to=davidsen@tmr.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.