From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org, elenstev@mesatop.com,
kbuild-devel@lists.sourceforge.net, Alan Cox <alan@redhat.com>
Subject: Re: Rename all derived CONFIG variables
Date: Mon, 12 Mar 2001 02:25:05 -0500 [thread overview]
Message-ID: <3AAC79D1.F9837EE7@mandrakesoft.com> (raw)
In-Reply-To: <20736.984380602@ocs3.ocs-net>
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
> are not used anywhere.
>
> ftp://ftp.ocs.com.au/pub/2.4.2-ac18-config_derived.gz
>
> is a 583,904 byte (unzipped) 114,291 (gzipped) patch which removes the
> unused variables and renames the 130 derived variables from CONFIG_FOO
> to CONFIG_FOO_DERIVED. The affected variables are :-
Not only do I think that CONFIG_xxx_DERIVED needlessly extends the name
of derived vars, but your patch does not belong in a stable series.
Derived CONFIG_xxx vars are likely to be referenced in source. Changing
those vars in the middle of a stable series pointlessly breaks external
source code.
I hope vendors don't start applying this patch...
Jeff
--
Jeff Garzik | "You see, in this world there's two kinds of
Building 1024 | people, my friend: Those with loaded guns
MandrakeSoft | and those who dig. You dig." --Blondie
next prev parent reply other threads:[~2001-03-12 7:26 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 [this message]
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
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=3AAC79D1.F9837EE7@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alan@redhat.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;
as well as URLs for NNTP newsgroup(s).