From: "Eric S. Raymond" <esr@thyrsus.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Peter Samuelson <peter@cadcamlab.org>,
"Eric S. Raymond" <esr@snark.thyrsus.com>,
linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: CML1 cleanup patch
Date: Mon, 26 Mar 2001 01:49:13 -0500 [thread overview]
Message-ID: <20010326014913.B11181@thyrsus.com> (raw)
In-Reply-To: <200103260001.f2Q01Yt09387@snark.thyrsus.com> <15038.56527.591553.87791@wire.cadcamlab.org> <3ABEE0B5.12A2F768@mandrakesoft.com>
In-Reply-To: <3ABEE0B5.12A2F768@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Mon, Mar 26, 2001 at 01:24:53AM -0500
Jeff Garzik <jgarzik@mandrakesoft.com>:
> > The -TOO suffix was to distinguish between this and the former 8139
> > driver, as the two coexisted in 2.2 and 2.3. As the old driver has
> > been dropped from 2.4, I propose likewise dropping the -TOO.
>
> It stays "8139too". Donald Becker's rtl8139.c continues to exist
> outside the kernel.
>
> And "rtl8139too" should have never crept into 2.2. That needs to be
> changed to "8139too." That's what I get for saying that I don't support
> 2.2...
Now, wait, Jeff. I'm not attached to Peter's change, but I don't think
we can reasonably be expected to worry about every possible driver
left over from every old version of Linux when managing the
configuration-symbol namespace. That way madness lies.
I'll cheerfully ship a supplementary patch to fix this one name later,
but we can't afford to have a wrangle over this bit of trivia delay
adoption of this one. I have a hell of a lot of work to do for
which this is critical path.
I left it pretty late as it is, out of hope that other people would
clean up some of the messes I noticed in the config namespace six
months ago, and they did -- but the 2.5 fork is nearly upon us and I
feel a strong need to get this in before then.
Would you and Peter please fight this out and tell me what to do in the
supplementary patch? I don't care, as long as the result has a non-numeric
prefix -- bare "8139whatever" is out.
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
Sometimes it is said that man cannot be trusted with the government
of himself. Can he, then, be trusted with the government of others?
-- Thomas Jefferson, in his 1801 inaugural address
next prev parent reply other threads:[~2001-03-26 6:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200103260001.f2Q01Yt09387@snark.thyrsus.com>
2001-03-26 6:08 ` CML1 cleanup patch Peter Samuelson
2001-03-26 6:24 ` Jeff Garzik
2001-03-26 6:42 ` Jeff Garzik
2001-03-26 7:09 ` Eric S. Raymond
2001-03-26 7:20 ` Jeff Garzik
2001-03-26 7:30 ` Eric S. Raymond
2001-03-26 7:37 ` Jeff Garzik
2001-03-26 7:28 ` [kbuild-devel] " Keith Owens
2001-03-26 7:43 ` Jeff Garzik
2001-03-26 7:52 ` Eric S. Raymond
2001-03-26 14:34 ` Rik van Riel
2001-03-26 6:49 ` Eric S. Raymond [this message]
2001-03-26 7:01 ` Jeff Garzik
2001-03-26 7:02 ` Alan Cox
2001-03-26 7:12 ` Eric S. Raymond
2001-03-26 14:43 ` Alan Cox
2001-03-26 7:22 ` Peter Samuelson
2001-03-26 7:40 ` Eric S. Raymond
2001-03-26 6:32 ` Eric S. Raymond
2001-03-26 11:57 ` [kbuild-devel] " John Cowan
2001-03-26 14:55 ` Rik van Riel
2001-03-26 17:54 ` Eric S. Raymond
2001-04-15 9:07 ` Kai Henningsen
2001-04-15 20:52 ` Olaf Titz
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=20010326014913.B11181@thyrsus.com \
--to=esr@thyrsus.com \
--cc=esr@snark.thyrsus.com \
--cc=jgarzik@mandrakesoft.com \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@cadcamlab.org \
/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