Messages in this thread |  | | Date | Sun, 02 Dec 2001 13:20:14 -0500 | From | Jeff Garzik <> | Subject | Re: Linux/Pro [was Re: Coding style - a non-issue] |
| |
Oliver Xymoron wrote: > > On Sun, 2 Dec 2001, Jeff Garzik wrote: > > > Oliver Xymoron wrote: > > > > > > On Sun, 2 Dec 2001, Alan Cox wrote: > > > > > > > > Please consider the following wipe out candidates as well: > > > > > > > > > > 2. proprietary CD-ROM > > > > > 3. xd.c (ridiculous isn't it?) > > > > > 4. old ide driver... > > > > > > > > I know people using all 3 of those, while bugs in some of the old scsi 8bit > > > > drivers went unnoticed for a year. > > > > > > We need a 'prompt for unmaintained drivers' trailing-edge option in the > > > build process so people will know when something's been orphaned and pick > > > it up. > > > > There's already CONFIG_OBSOLETE... > > And it's practically obsolete itself, outside of the ARM directory. What > I'm proposing is something in the Code Maturity menu that's analogous to > EXPERIMENTAL along with a big (UNMAINTAINED) marker next to unmaintained > drivers. Obsolete and unmaintained and deprecated all mean slightly > different things, by the way. So the config option would probably say > 'Show obsolete, unmaintained, or deprecated items?' and mark each item > appropriately. Anything that no one made a fuss about by 2.7 would be > candidates for removal.
The idea behind CONFIG_OBSOLETE is supposed to be that it does not actually appear as a Y/N option. You enclose a Config.in option with that, and it disappears
But I'm all for removing old stuff. There is no reason to keep something that flat out doesn't work and hasn't for a long long time... if somebody wants to pick it up they can grab linux-2.2 or linux-2.0 from any FTP mirror.
Jeff
-- Jeff Garzik | Only so many songs can be sung Building 1024 | with two lips, two lungs, and one tongue. MandrakeSoft | - nomeansno
- 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/
|  |