From: Philipp Rumpf <prumpf@mandrakesoft.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org, elenstev@mesatop.com,
kbuild-devel@lists.sourceforge.net
Subject: Re: Rename all derived CONFIG variables
Date: Mon, 12 Mar 2001 05:37:40 -0600 [thread overview]
Message-ID: <20010312053740.C16340@mandrakesoft.mandrakesoft.com> (raw)
In-Reply-To: <20736.984380602@ocs3.ocs-net>
In-Reply-To: <20736.984380602@ocs3.ocs-net>; from Keith Owens on Mon, Mar 12, 2001 at 06:03:22PM +1100
On Mon, Mar 12, 2001 at 06:03:22PM +1100, Keith Owens wrote:
> In 2.4.2-ac18 there are 130 CONFIG options that are always derived from
> other options, the user has no control over them. It is useful for the
> kernel build process to know which variables are derived and which
> variables the user can control. There are also 6 CONFIG options that
Yes, it is. However, I don't see a reason to use a different namespace
for them. At least some of the options below might become non-derived
options again, and having that knowledge spread out over most of the
kernel tree doesn't make any sense to me.
next prev parent reply other threads:[~2001-03-12 11:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-12 7:03 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
2001-03-12 11:37 ` Philipp Rumpf [this message]
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=20010312053740.C16340@mandrakesoft.mandrakesoft.com \
--to=prumpf@mandrakesoft.com \
--cc=elenstev@mesatop.com \
--cc=kaos@ocs.com.au \
--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®