From: "Eric S. Raymond" <esr@thyrsus.com>
To: Rogier Wolff <R.E.Wolff@BitWizard.nl>
Cc: Richard Gooch <rgooch@atnf.csiro.au>,
"Edward S. Marshall" <esm@logic.net>,
Rik van Riel <riel@conectiva.com.br>,
linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: [kbuild-devel] Re: Cross-referencing frenzy
Date: Thu, 19 Apr 2001 09:36:13 -0400 [thread overview]
Message-ID: <20010419093613.A32121@thyrsus.com> (raw)
In-Reply-To: <20010419013748.C29686@thyrsus.com> <200104190926.LAA06753@cave.bitwizard.nl>
In-Reply-To: <200104190926.LAA06753@cave.bitwizard.nl>; from R.E.Wolff@BitWizard.nl on Thu, Apr 19, 2001 at 11:26:08AM +0200
Rogier Wolff <R.E.Wolff@BitWizard.nl>:
> I think it should be possible to do:
>
> /* to enable the special stuff, change the "undef" to "define",
> If you really want you can add this to Config.in so that you're presented
> with this choice when configuring your kernel. But it's not neccesary
> for the general public to always see this toggle. */
> #undef CONFIG_SX_SPECIALSTUFF
>
> #ifdef CONFIG_SX_SPECIALSTUFF
> ...
>
> #endif
Yes, I could write and test code to handle this in about twenty minutes.
And I was about to do it when I realized that it would be the wrong thing.
The right answer is that CONFIG_SX_SPECIALSTUFF *should* be flagged as
an error -- because it doesn't belong in the CONFIG_ namespace, which
by definition should be reserved for things the configurators control.
It should be called something else: perhaps ENABLE_SX_SPECIALSTUFF
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
The IRS has become morally corrupted by the enormous power which we in
Congress have unwisely entrusted to it. Too often it acts like a
Gestapo preying upon defenseless citizens.
-- Senator Edward V. Long
next prev parent reply other threads:[~2001-04-19 14:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-19 3:34 Cross-referencing frenzy Eric S. Raymond
2001-04-19 4:00 ` Richard Gooch
2001-04-19 4:11 ` Rik van Riel
2001-04-19 4:36 ` Edward S. Marshall
2001-04-19 5:06 ` Richard Gooch
2001-04-19 5:37 ` Eric S. Raymond
2001-04-19 9:26 ` Rogier Wolff
2001-04-19 13:36 ` Eric S. Raymond [this message]
2001-04-19 15:22 ` [kbuild-devel] " Rogier Wolff
2001-04-19 5:38 ` Jeff Garzik
2001-04-19 5:32 ` Eric S. Raymond
2001-04-19 11:41 ` Alan Cox
2001-04-19 4:49 ` Andreas Dilger
2001-04-19 13:23 ` Mike Castle
2001-04-19 13:36 ` Alan Cox
2001-04-19 17:33 ` Eric S. Raymond
2001-04-19 20:53 ` Jim Treadway
2001-04-19 8:02 ` Russell King
2001-04-19 13:16 ` Eric S. Raymond
2001-04-19 14:17 ` Jeff Garzik
2001-04-19 14:25 ` Eric S. Raymond
2001-04-19 18:49 ` [kbuild-devel] " Peter Samuelson
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=20010419093613.A32121@thyrsus.com \
--to=esr@thyrsus.com \
--cc=R.E.Wolff@BitWizard.nl \
--cc=esm@logic.net \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@atnf.csiro.au \
--cc=riel@conectiva.com.br \
/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