mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Samuelson <peter@cadcamlab.org>
To: 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 01:22:04 -0600 (CST)	[thread overview]
Message-ID: <15038.60956.18563.327332@wire.cadcamlab.org> (raw)
In-Reply-To: <200103260001.f2Q01Yt09387@snark.thyrsus.com> <15038.56527.591553.87791@wire.cadcamlab.org> <3ABEE0B5.12A2F768@mandrakesoft.com> <20010326014913.B11181@thyrsus.com>


  [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.

[esr]
> 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.

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?

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?

Peter

  parent reply	other threads:[~2001-03-26  7:23 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 ` 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 [this message]
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=15038.60956.18563.327332@wire.cadcamlab.org \
    --to=peter@cadcamlab.org \
    --cc=esr@snark.thyrsus.com \
    --cc=jgarzik@mandrakesoft.com \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®