netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gabriel C <crazy@pimpmylinux.org>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	netdev@vger.kernel.org
Subject: Re: [PATCH] net/, drivers/net/ , missing EXPERIMENTAL in menus
Date: Wed, 18 Jul 2007 22:48:02 +0200	[thread overview]
Message-ID: <469E7C82.5020400@pimpmylinux.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0707181620460.13912@localhost.localdomain>

Robert P. J. Day wrote:
> On Wed, 18 Jul 2007, Gabriel C wrote:
> 
>> Everything 'depends on' EXPERIMENTAL should be marked as such,
>> visible in the menus.
> 
> rather than add all that extraneous dreck to the Kconfig files, i
> *really* wish folks would give serious thought to my earlier
> suggestion about a "maturity level" attribute that could be used to
> not only add a parenthesized maturity level during display, but could
> also be used to activate/deactivate entire levels in one operation.
> 
> there's no point adding all that redundant content when it can all be
> done automatically.


I don't know what your suggestion was , I'm sorry.

It may be for sure a good idea to add all this maturity levels
automatically but for now such an thing does not exists.

> 
> rday


Gabriel

      parent reply	other threads:[~2007-07-18 20:49 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-18 20:18 [PATCH] net/, drivers/net/ , missing EXPERIMENTAL in menus Gabriel C
2007-07-18 20:23 ` Robert P. J. Day
2007-07-18 20:40   ` Randy Dunlap
2007-07-18 20:44     ` Robert P. J. Day
2007-07-18 20:45     ` Jeff Garzik
2007-07-18 20:51       ` Robert P. J. Day
2007-07-18 21:09         ` Adrian Bunk
2007-07-18 21:18           ` Robert P. J. Day
2007-07-19  5:47             ` Adrian Bunk
2007-07-19  7:33               ` Robert P. J. Day
2007-07-19  8:42                 ` Stefan Richter
2007-07-19  9:25                   ` Robert P. J. Day
2007-07-19 13:53                     ` Stefan Richter
2007-07-19 15:31                     ` Randy Dunlap
2007-07-19 16:19                       ` Robert P. J. Day
2007-07-19 22:05                         ` Simon Arlott
2007-07-19 22:28                           ` Robert P. J. Day
2007-08-31 17:25                           ` Randy Dunlap
2007-08-31 17:23                             ` Robert P. J. Day
2007-08-31 18:06                               ` Jeff Garzik
2007-08-31 19:29                                 ` Jan Engelhardt
2007-08-31 20:16                                 ` Randy Dunlap
2007-08-31 21:00                                   ` Robert P. J. Day
2007-08-31 21:25                                     ` Randy Dunlap
2007-08-31 20:49                                 ` Robert P. J. Day
2007-08-31 22:01                                   ` Jeff Garzik
2007-08-31 22:10                                     ` Robert P. J. Day
2007-09-01 10:44                             ` Robert P. J. Day
2007-09-01 12:49                               ` Sam Ravnborg
2007-09-01 12:56                                 ` Robert P. J. Day
2007-07-18 21:28           ` Robert P. J. Day
2007-07-18 20:52       ` Randy Dunlap
2007-07-18 20:48   ` Gabriel C [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=469E7C82.5020400@pimpmylinux.org \
    --to=crazy@pimpmylinux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rpjday@mindspring.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;
as well as URLs for NNTP newsgroup(s).