public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: John Richard Moser <nigelenki@comcast.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROPOSAL:  New NEW development model
Date: Tue, 26 Oct 2004 10:47:30 -0700	[thread overview]
Message-ID: <20041026174730.GL17038@holomorphy.com> (raw)
In-Reply-To: <417E8422.3020009@comcast.net>

On Tue, Oct 26, 2004 at 01:06:42PM -0400, John Richard Moser wrote:
> In lieu of the recent unpleasantness[1] about the new development model,
> and of some unexpected nastiness[2] as well, I propose that a very
> slight modification be made to the current development model.  This
> would merge the previous and new development models (as far as my
> understanding is on them) and create a solution for all.
> [1] http://lkml.org/lkml/2004/10/22/497
> [2] http://lkml.org/lkml/2004/10/26/155
> Previously, there were "Stable" and "Development" branches.  The
> "Stable" branches, such as 2.2 and 2.4, would stagnate, and rarely have
> backported features.  The "Development" branches such as 2.3 and 2.5
> would be hammered and mixed with patches, then cleaned up until they
> were fairly stable.  Then they'd be hammered with more patches, then
> cleaned up, then frozen, cleaned up until "stable" and then released.

This is not useful to distinguish your "suggestion" from the status quo.


-- wli

  reply	other threads:[~2004-10-26 17: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 [this message]
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

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=20041026174730.GL17038@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nigelenki@comcast.net \
    /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