From: "Eric S. Raymond" <esr@thyrsus.com>
To: Peter Samuelson <peter@cadcamlab.org>
Cc: Eric Raymond <esr@snark.thyrsus.com>,
Jeff Garzik <jgarzik@mandrakesoft.com>,
linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: CML1 cleanup patch
Date: Mon, 26 Mar 2001 02:40:52 -0500 [thread overview]
Message-ID: <20010326024052.C12481@thyrsus.com> (raw)
In-Reply-To: <200103260001.f2Q01Yt09387@snark.thyrsus.com> <15038.56527.591553.87791@wire.cadcamlab.org> <3ABEE0B5.12A2F768@mandrakesoft.com> <20010326014913.B11181@thyrsus.com> <15038.60956.18563.327332@wire.cadcamlab.org>
In-Reply-To: <15038.60956.18563.327332@wire.cadcamlab.org>; from peter@cadcamlab.org on Mon, Mar 26, 2001 at 01:22:04AM -0600
Peter Samuelson <peter@cadcamlab.org>:
>
> [Jeff Garzik]
> > > It stays "8139too". Donald Becker's rtl8139.c continues to exist
> > > outside the kernel.
>
> Honestly, Jeff, I don't see how it matters -- because if you are
> downloading an external driver, you are not going through the config
> system anyway.
>
> But ... "maintanicus selector est" (my pseudo-Latin for "the maintainer
> gets to choose") so I support your stand.
And that's an argument I can buy, too. I'll restore the TOO prefix
in my change list.
> Eric, the issue arose because you are obliquely proposing -- nay,
> insisting on -- a policy change. CONFIG_8139TOO is a perfectly valid
> preprocessor token and a perfectly valid GNU Make macro name. It
> corresponds with a source file '8139too.c' which is also perfectly
> valid.
>
> Did it never occur to you that by insisting on a policy change (and
> related code changes), with no discussion, consensus or mandate, and
> which fixes no current bugs ... that a few toes may feel stepped on?
Actually, that's not what I did. One of the principal PPC maintainers
agreed to get the PPC numeric-prefix symbols (9 of the 20) cleaned up,
but dropped the ball. I waited on this as long as I thought I could.
> The burden of proof is yours. Why should a CML2 design decision
> (stripping of CONFIG_ in the configuration files) change what seems to
> be an entirely reasonable policy? Especially since there are multiple
> ways, which you have rejected, to work around the lexical problem in
> CML2 itself?
The workarounds would be slow, or ugly, or both. As I said -- I might
have gone with them, but there since had to be a fix patch anyway, and
I had buy-in for all but 11 of the 39 changes...
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
According to the National Crime Survey administered by the Bureau of
the Census and the National Institute of Justice, it was found that
only 12 percent of those who use a gun to resist assault are injured,
as are 17 percent of those who use a gun to resist robbery. These
percentages are 27 and 25 percent, respectively, if they passively
comply with the felon's demands. Three times as many were injured if
they used other means of resistance.
-- G. Kleck, "Policy Lessons from Recent Gun Control Research,"
next prev parent reply other threads:[~2001-03-26 7:38 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
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 [this message]
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=20010326024052.C12481@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