Re: second thoughts about DEPRECATED and OBSOLETE maturity levels

2007-03-01 Thread Robert P. J. Day
On Mon, 26 Feb 2007, Sam Ravnborg wrote: > On Sun, Feb 25, 2007 at 05:07:24PM -0500, Robert P. J. Day wrote: > > > > having championed the cause of adding those two code maturity levels > > to init/Kconfig, i just realized that implementing them as simple > > dependencies has a *really* annoying

Re: second thoughts about DEPRECATED and OBSOLETE maturity levels

2007-02-26 Thread Robert P. J. Day
On Mon, 26 Feb 2007, Sam Ravnborg wrote: > On Sun, Feb 25, 2007 at 05:07:24PM -0500, Robert P. J. Day wrote: > > > > having championed the cause of adding those two code maturity levels > > to init/Kconfig, i just realized that implementing them as simple > > dependencies has a *really* annoying

Re: second thoughts about DEPRECATED and OBSOLETE maturity levels

2007-02-26 Thread Sam Ravnborg
On Sun, Feb 25, 2007 at 05:07:24PM -0500, Robert P. J. Day wrote: > > having championed the cause of adding those two code maturity levels > to init/Kconfig, i just realized that implementing them as simple > dependencies has a *really* annoying shortcoming. > > in order to display that a ker

second thoughts about DEPRECATED and OBSOLETE maturity levels

2007-02-25 Thread Robert P. J. Day
having championed the cause of adding those two code maturity levels to init/Kconfig, i just realized that implementing them as simple dependencies has a *really* annoying shortcoming. in order to display that a kernel config feature is experimental, developers have not only made that feature