All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: maturity and status and attributes, oh my!
Date: Sat, 1 Sep 2007 14:24:41 -0400	[thread overview]
Message-ID: <20070901182441.GA8571@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0709011402570.20725@localhost.localdomain>

On Sat, Sep 01, 2007 at 02:06:22PM -0400, Robert P. J. Day wrote:
 > On Sat, 1 Sep 2007, Robert P. J. Day wrote:
 > 
 > > On Sat, 1 Sep 2007, Dave Jones wrote:
 > 
 > > > People just don't care about how mature an option is if they need
 > > > a driver/feature.  *No-one* is going to come across options and
 > > > think "Oh, the driver for my network card isn't stable. Guess I'll
 > > > not enable it". And the idea of hiding the options behind multiple
 > > > levels of maturity options sounds completely batshit.
 > 
 > by the way and just for the record, dave, you have the above
 > completely backwards.  the default for what you would be allowed to
 > select or deselect would be *everything*.  what this whole maturity
 > level thing would allow you to do is selectively *deselect* (or
 > *filter*) what is displayed.  in short, if you do nothing, you see no
 > effect.

>From your earlier mail..

"all this new construct is doing is implementing a new way to globally
 select or de-select large sets of kernel features to display for user
 selection, in exactly the way that EXPERIMENTAL does it now, that's all."
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

EXPERIMENTAL hides options.

 > so i don't mind folks criticizing the proposal.  but it sure would be
 > nice if they understood what they were criticising, know what i mean?

Quite.

	Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2007-09-01 18:24 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-31 21:38 maturity and status and attributes, oh my! Robert P. J. Day
2007-08-31 22:02 ` Jeff Garzik
2007-09-01  6:35   ` Jan Engelhardt
2007-09-01  9:06     ` Robert P. J. Day
2007-08-31 22:36 ` Stefan Richter
2007-09-01  1:23   ` Robert P. J. Day
2007-09-01  9:14     ` Stefan Richter
2007-09-01  9:21       ` Robert P. J. Day
2007-09-01  9:47         ` Stefan Richter
2007-09-01  9:54           ` Robert P. J. Day
2007-09-01 13:14           ` Jan Engelhardt
2007-09-01 13:53             ` Jeff Garzik
2007-09-01 10:43       ` Jeff Garzik
2007-09-01 10:52         ` Robert P. J. Day
2007-09-01 11:06           ` Jeff Garzik
2007-09-01 13:44             ` Bartlomiej Zolnierkiewicz
2007-09-01 13:52               ` Jeff Garzik
2007-09-01 14:27               ` Stefan Richter
     [not found]   ` <Pine.LNX.4.64.0709010435070.26137@localhost.localdomain>
2007-09-01  9:27     ` Stefan Richter
2007-09-01  9:41       ` Robert P. J. Day
2007-09-01 17:22         ` Dave Jones
2007-09-01 17:58           ` Robert P. J. Day
2007-09-01 18:06             ` Robert P. J. Day
2007-09-01 18:24               ` Dave Jones [this message]
2007-08-31 23:02 ` Dave Jones
2007-09-01  8:34   ` Robert P. J. Day
  -- strict thread matches above, loose matches on Subject: below --
2007-08-31 23:29 Mitchell Erblich
2007-09-01  1:33 ` Robert P. J. Day
2007-09-01  6:39   ` Jan Engelhardt
2007-09-01  7:02     ` Robert P. J. Day

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=20070901182441.GA8571@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@mindspring.com \
    --cc=stefanr@s5r6.in-berlin.de \
    /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.