[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070831142553.541ade40.rdunlap@xenotime.net>
Date: Fri, 31 Aug 2007 14:25:53 -0700
From: Randy Dunlap <rdunlap@...otime.net>
To: "Robert P. J. Day" <rpjday@...dspring.com>
Cc: Jeff Garzik <jeff@...zik.org>, Simon Arlott <simon@...e.lp0.eu>,
sam@...nborg.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Stefan Richter <stefanr@...6.in-berlin.de>,
Adrian Bunk <bunk@...sta.de>,
Gabriel C <crazy@...pmylinux.org>, netdev@...r.kernel.org
Subject: Re: [PATCH] net/, drivers/net/ , missing EXPERIMENTAL in menus
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 ***
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists