From: Oliver Xymoron <oxymoron@waste.org>
To: Keith Owens <kaos@ocs.com.au>
Cc: <esr@thyrsus.com>, Peter Samuelson <peter@cadcamlab.org>,
<linux-kernel@vger.kernel.org>, <elenstev@mesatop.com>,
<kbuild-devel@lists.sourceforge.net>
Subject: Re: [kbuild-devel] Re: Rename all derived CONFIG variables
Date: Wed, 14 Mar 2001 15:34:19 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.30.0103141527370.4691-100000@waste.org> (raw)
In-Reply-To: <24972.984388704@ocs3.ocs-net>
On Mon, 12 Mar 2001, Keith Owens wrote:
> On Mon, 12 Mar 2001 03:53:07 -0500,
> "Eric S. Raymond" <esr@thyrsus.com> wrote:
> >But if we're going to push Linus and the kernel crew to switch to
> >CML2, then why invite the political tsuris of trying to get a large
> >patch into 2.4 now? Maybe I'm missing something here, but this doesn't
> >seem necessary to me.
>
> The derived config variables should be in a separate name space,
> whether config is CML1 or CML2. This patch does it for CML1.
I don't think this makes sense at all. The derivation of the config
values is the concern of the configuration system, not the code.
Consider something like CONFIG_CPU_HAS_FEATURE_FOO that might currently be
derived from CONFIG_CPU_BAR but may in the future be made independent. Or
vice-versa. Your proposed name-change means additional maintenance
headache and gets you nothing that you couldn't get by simply including
whatever script you wrote to deduce the dependencies. Such a script would
at least be able to tell you what a variable was derived from.
--
"Love the dolphins," she advised him. "Write by W.A.S.T.E.."
next prev parent reply other threads:[~2001-03-14 21:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-12 7:03 Rename all derived CONFIG variables Keith Owens
2001-03-12 7:25 ` Jeff Garzik
2001-03-12 14:24 ` Alan Cox
2001-03-12 8:26 ` Peter Samuelson
2001-03-12 8:53 ` [kbuild-devel] " Eric S. Raymond
2001-03-12 9:18 ` Keith Owens
2001-03-12 14:28 ` Alan Cox
2001-03-14 21:34 ` Oliver Xymoron [this message]
2001-03-12 11:37 ` Philipp Rumpf
2001-03-12 12:12 ` Hugh Dickins
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=Pine.LNX.4.30.0103141527370.4691-100000@waste.org \
--to=oxymoron@waste.org \
--cc=elenstev@mesatop.com \
--cc=esr@thyrsus.com \
--cc=kaos@ocs.com.au \
--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;
as well as URLs for NNTP newsgroup(s).