Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966052AbXHaVNy (ORCPT ); Fri, 31 Aug 2007 17:13:54 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1761247AbXHaVNl (ORCPT ); Fri, 31 Aug 2007 17:13:41 -0400 Received: from nic.NetDirect.CA ([216.16.235.2]:43921 "EHLO rubicon.netdirect.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1761114AbXHaVNk (ORCPT ); Fri, 31 Aug 2007 17:13:40 -0400 X-Originating-Ip: 72.143.66.27 Date: Fri, 31 Aug 2007 17:00:57 -0400 (EDT) From: "Robert P. J. Day" X-X-Sender: rpjday@localhost.localdomain To: Randy Dunlap cc: Jeff Garzik , Simon Arlott , sam@ravnborg.org, Linux Kernel Mailing List , Stefan Richter , Adrian Bunk , Gabriel C , netdev@vger.kernel.org Subject: Re: [PATCH] net/, drivers/net/ , missing EXPERIMENTAL in menus In-Reply-To: <20070831131612.312664ef.rdunlap@xenotime.net> Message-ID: 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 X-Net-Direct-Inc-MailScanner-Information: Please contact the ISP for more information X-Net-Direct-Inc-MailScanner: Found to be clean X-Net-Direct-Inc-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-16.8, required 5, autolearn=not spam, ALL_TRUSTED -1.80, BAYES_00 -15.00, INIT_RECVD_OUR_AUTH -20.00, RCVD_IN_SORBS_DUL 20.00) X-Net-Direct-Inc-MailScanner-From: rpjday@mindspring.com Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1595 Lines: 43 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. rday -- ======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA http://crashcourse.ca ======================================================================== - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/