From mboxrd@z Thu Jan 1 00:00:00 1970 From: Randy Dunlap Subject: Re: [PATCH] net/, drivers/net/ , missing EXPERIMENTAL in menus Date: Fri, 31 Aug 2007 14:25:53 -0700 Message-ID: <20070831142553.541ade40.rdunlap@xenotime.net> References: <469E75AA.7040109@pimpmylinux.org> <20070718134012.cde2f956.randy.dunlap@oracle.com> <469E7BE1.6090401@garzik.org> <20070718210903.GM3801@stusta.de> <20070719054742.GN3801@stusta.de> <469F240E.9040205@s5r6.in-berlin.de> <20070719083109.13b2ab56.rdunlap@xenotime.net> <469FE045.3070403@simon.arlott.org.uk> <20070831102527.09fb42c0.rdunlap@xenotime.net> <46D858A9.4080506@garzik.org> <20070831131612.312664ef.rdunlap@xenotime.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Jeff Garzik , Simon Arlott , sam@ravnborg.org, Linux Kernel Mailing List , Stefan Richter , Adrian Bunk , Gabriel C , netdev@vger.kernel.org To: "Robert P. J. Day" Return-path: Received: from xenotime.net ([66.160.160.81]:58606 "HELO xenotime.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S965450AbXHaVZ6 (ORCPT ); Fri, 31 Aug 2007 17:25:58 -0400 Received: from midway.site ([96.225.192.201]) by xenotime.net for ; Fri, 31 Aug 2007 14:25:53 -0700 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Fri, 31 Aug 2007 17:00:57 -0400 (EDT) Robert P. J. Day wrote: > On Fri, 31 Aug 2007, Randy Dunlap wrote: > > > What I like about the patch is that it associates some kconfig > > symbol with prompt strings, so that we don't have to edit > > "(EXPERIMENTAL)" all the darn time (e.g.). > > > > I'd be quite happy with calling it "status" rather than "maturity", > > and with being able to use multiple of the status tags at one time, > > such as > > > > config FOO > > depends on BAR > > status OBSOLETE BROKEN > > grrrrrrrr ... i already made my point in my earlier post. i'd > really, really like it if *this* attribute remained as "maturity". an > entirely *separate* attribute could be defined as a feature "status", > which would be entirely orthogonal to maturity level, so that the > above would be written as > > maturity OBSOLETE > status BROKEN > > there's a reason for this -- any feature should have exactly *one* > value for any attribute. that is, in terms of maturity, a feature > could be EXPERIMENTAL *or* DEPRECATED *or* OBSOLETE. it ***can't*** > be more than one, as in both DEPRECATED *and* OBSOLETE. to allow that > flexibility is to descend into absurdity. If Simon (or anyone else) continues to work on it, I'll leave this decision up to them... --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code ***