On Wed, 17 Jan 2007 17:04:20 EST, "Robert P. J. Day" said: > > How much of the 'OBSOLETE' code should just be labelled 'BROKEN' > > instead? > > the stuff that's actually "broken." :-) Right - the question is how much code qualifies as either/both, and which we should use when we encounter the random driver that's both obsolete *and* broken...
Attachment:
pgptrXIEDDXJ2.pgp
Description: PGP signature
- Follow-Ups:
- Re: "obsolete" versus "deprecated", and a new config option?
- From: "Robert P. J. Day" <[email protected]>
- Re: "obsolete" versus "deprecated", and a new config option?
- References:
- "obsolete" versus "deprecated", and a new config option?
- From: "Robert P. J. Day" <[email protected]>
- Re: "obsolete" versus "deprecated", and a new config option?
- From: [email protected]
- Re: "obsolete" versus "deprecated", and a new config option?
- From: "Robert P. J. Day" <[email protected]>
- "obsolete" versus "deprecated", and a new config option?
- Prev by Date: [PATCH] Add new categories of DEPRECATED and OBSOLETE.
- Next by Date: [PATCH: 2.6.20-rc4-mm1] JFS: Avoid deadlock introduced by explicit I/O plugging
- Previous by thread: Re: "obsolete" versus "deprecated", and a new config option?
- Next by thread: Re: "obsolete" versus "deprecated", and a new config option?
- Index(es):
 |