On Sun, 18 Feb 2007 19:35:07 +0100, Bartlomiej Zolnierkiewicz wrote: > I think that the patch is useful and that the distinction between > DEPRECATED and OBSOLETE options is quite clear: > > * DEPRECATED == new better code is available, old code scheduled for removal > > * OBSOLETE == no replacement yet but the code is broken by design > and unreliable, not scheduled for removal yet 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 * OBSOLETE == replacement available, no reason to use this code anymore -- Tilman Schmidt E-Mail: [email protected] Bonn, Germany Diese Nachricht besteht zu 100% aus wiederverwerteten Bits. Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
Attachment:
signature.asc
Description: OpenPGP digital signature
- Follow-Ups:
- Re: [PATCH] kbuild: Add the code maturity levels DEPRECATED and OBSOLETE.
- From: "Robert P. J. Day" <[email protected]>
- Re: [PATCH] kbuild: Add the code maturity levels DEPRECATED and OBSOLETE.
- From: Bartlomiej Zolnierkiewicz <[email protected]>
- Re: [PATCH] kbuild: Add the code maturity levels DEPRECATED and OBSOLETE.
- References:
- [PATCH] kbuild: Add the code maturity levels DEPRECATED and OBSOLETE.
- From: "Robert P. J. Day" <[email protected]>
- Re: [PATCH] kbuild: Add the code maturity levels DEPRECATED and OBSOLETE.
- From: Bartlomiej Zolnierkiewicz <[email protected]>
- [PATCH] kbuild: Add the code maturity levels DEPRECATED and OBSOLETE.
- Prev by Date: Re: [PATCH] Eliminate user-selectable CONFIG_MV643XX_ETH_[012]
- Next by Date: Re: [PATCH] aio: propogate post-EIOCBQUEUED errors to completion event
- Previous by thread: Re: [PATCH] kbuild: Add the code maturity levels DEPRECATED and OBSOLETE.
- Next by thread: Re: [PATCH] kbuild: Add the code maturity levels DEPRECATED and OBSOLETE.
- Index(es):
 |