From: Jeff Garzik <jgarzik@pobox.com>
To: Patrick Finnegan <pat@purdueriots.com>
Cc: Dan Kegel <dank@kegel.com>, john slee <indigoid@higherplane.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Why can't Johnny compile?
Date: Sat, 16 Nov 2002 01:10:45 -0500 [thread overview]
Message-ID: <3DD5E165.20402@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0211160059540.16668-100000@ibm-ps850.purdueriots.com>
Patrick Finnegan wrote:
> Wouldn't it then seem reasonable to remove things from the kernel that
> have been broken for a long time, and no one seems to care enough to fix?
> I know of at least one driver (IOmega Buz v4l) that seems to have fallen
> into disrepair possibly since before 2.4.0, and as far as I know has not
> been repaired since then.
That's really a matter of taste... a lot of Linux hackers seem to enjoy
retrocomputing and keeping old things around just in case. Just in case
somebody sees you post, for example, and gets motivated to fix IOmega
Buz :) Some things do get removed though, every now and then.
We have CONFIG_OBSOLETE as a pseudo-config option around which we may
deprecate drivers. If a major version or two passes with no one
complaining, we can remove the driver then...
Jeff
next prev parent reply other threads:[~2002-11-16 6:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-16 5:35 Why can't Johnny compile? Dan Kegel
2002-11-16 5:49 ` Jeff Garzik
2002-11-16 6:04 ` Patrick Finnegan
2002-11-16 6:10 ` Jeff Garzik [this message]
2002-11-16 6:15 ` William Lee Irwin III
2002-11-17 5:34 ` Ralf Baechle
2002-11-16 9:47 ` Kai Henningsen
2002-11-16 14:37 ` Arnaldo Carvalho de Melo
2002-11-16 15:11 ` john slee
2002-11-16 6:23 ` Arnaldo Carvalho de Melo
2002-11-16 19:14 ` Nathan
2002-11-16 21:04 ` Jeff Garzik
2002-11-16 21:37 ` Arnaldo Carvalho de Melo
2002-11-16 21:42 ` Arnaldo Carvalho de Melo
2002-11-16 23:51 ` Alan Cox
2002-11-17 0:09 ` Dan Kegel
2002-11-17 0:08 ` romieu
2002-11-17 3:18 ` Patrick Finnegan
2002-11-17 0:18 ` Nathan
2002-11-17 0:43 ` Alan Cox
2002-11-18 21:02 ` Bill Davidsen
2002-11-18 23:12 ` Alan Cox
2002-11-19 16:30 ` Bill Davidsen
2002-11-19 16:36 ` Jeff Garzik
2002-11-19 17:29 ` Alan Cox
2002-11-19 18:01 ` David G Hamblen
2002-11-19 19:34 ` Alan Cox
2002-11-17 1:34 ` Adam Kropelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3DD5E165.20402@pobox.com \
--to=jgarzik@pobox.com \
--cc=dank@kegel.com \
--cc=indigoid@higherplane.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pat@purdueriots.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox