Messages in this thread | | | Date | Tue, 20 Feb 2007 18:23:22 -0500 (EST) | From | "Robert P. J. Day" <> | Subject | Re: [PATCH] kbuild: Add the code maturity levels DEPRECATED and OBSOLETE. |
| |
On Wed, 21 Feb 2007, Tilman Schmidt wrote:
> Am 20.02.2007 23:52 schrieb Robert P. J. Day: > > "deprecated" means that there *is* a complete replacement available > > *right now* and you should consider switching to it. > > > > if you can't offer someone a completely functional, better alternative > > to what they're using now, then you can't say that what they're using > > now is deprecated. > > So, to take a specific example (incidentally the one I am > personally interested in): > > isdn4linux (CONFIG_ISDN_I4L), currently marked as "obsolete" > (which is undoubtedly incorrect), would not even qualify as > "deprecated" as long as its successor, the CAPI 2.0 subsystem > (CONFIG_ISDN_CAPI) doesn't support all the hardware currently > supported by old i4l. > > Or did I misunderstand something there?
IMHO, unless you have a fully-functional replacement ready to go, you can't call something "deprecated" much less "obsolete". so, yes, calling isdn4linux "obsolete" is hideously premature.
rday -- ======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA
http://fsdev.net/wiki/index.php?title=Main_Page ======================================================================== - 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/
| |