Messages in this thread |  | | Date | Tue, 20 Feb 2007 17:52:27 -0500 (EST) | From | "Robert P. J. Day" <> | Subject | Re: [PATCH] kbuild: Add the code maturity levels DEPRECATED and OBSOLETE. |
| |
On Tue, 20 Feb 2007, Bartlomiej Zolnierkiewicz wrote:
> > On Tuesday 20 February 2007 17:27, Tilman Schmidt wrote:
> > Is that really the consensus on these definitions? I thought it was > > more or less the opposite: > > > > * DEPRECATED == no (complete) replacement available yet, but it has > > been decided that this code is less than optimal and > > alternatives should be preferred
just to clarify this, that's not my idea of "deprecated". "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.
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/
|  |