public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
To: John Richard Moser <nigelenki@comcast.net>
Cc: Josh Boyer <jdub@us.ibm.com>,
	William Lee Irwin III <wli@holomorphy.com>,
	linux-kernel@vger.kernel.org
Subject: Re: PROPOSAL:  New NEW development model
Date: Tue, 26 Oct 2004 17:56:41 -0400	[thread overview]
Message-ID: <417EC819.7030809@tmr.com> (raw)
In-Reply-To: <417EA486.7070105@comcast.net>

John Richard Moser wrote:

> Still, a month or two to adapt to a new task scheduler out of 6 months
> leaves 4-5 months per stable release if the Volatile branch decides to
> hack up the scheduler.  This is still a better scenario then "VM and
> scheduler infrastructures may change on any given release."
> 
> 
> 
> So OK, that's what's good here; so what's wrong with it?  We've already
> established that there will be a minimal level of added work for a
> maintainer to keep the Stable up.  Are there any other drawbacks?  If
> not, any objections to trying to sell this one to Linus and Andrew?  :)

Knock yourself out, I would be happy if they would just agree not to 
take features out of a stable series or intentionally break them. If new 
features don't break the old ones I don't think there's a persuasive 
argument to keep them out.

-- 
    -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-10-26 21:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-26 17:06 PROPOSAL: New NEW development model John Richard Moser
2004-10-26 17:47 ` William Lee Irwin III
2004-10-26 18:24   ` John Richard Moser
2004-10-26 19:08     ` Josh Boyer
2004-10-26 19:24       ` John Richard Moser
2004-10-26 21:56         ` Bill Davidsen [this message]

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=417EC819.7030809@tmr.com \
    --to=davidsen@tmr.com \
    --cc=jdub@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wli@holomorphy.com \
    /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