From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: elenstev@mesatop.com, linux-kernel@vger.kernel.org
Subject: Re: List of recent (2.4.0 to 2.4.2-ac18) CONFIG options needing Configure.help text.
Date: Sun, 11 Mar 2001 02:08:15 -0500 [thread overview]
Message-ID: <3AAB245F.A98004D9@mandrakesoft.com> (raw)
In-Reply-To: <15167.984293552@ocs3.ocs-net>
Keith Owens wrote:
>
> On Sat, 10 Mar 2001 23:03:19 -0700,
> Steven Cole <elenstev@mesatop.com> wrote:
> >With the 2.4.0 kernel, there were 476 CONFIG options which had
> >no help entry in Configure.help. With 2.4.2-ac18, this number is now 547,
> >which has been kept this low with 54 options getting Configure.help text.
>
> If any of these CONFIG_ options are always derived (i.e. the user never
> sees them on a config menu) then please add the suffix _DERIVED to such
> options. They still need to start with CONFIG_ to suit the kernel
> build dependency generator so we cannot change the start of the name.
> Appending _DERIVED will make it obvious that the options require no
> help text.
Yow. That is very cumbersome. Can't you just keep a list somewhere,
instead of making such options longer?
--
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-11 7:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-11 6:03 List of recent (2.4.0 to 2.4.2-ac18) CONFIG options needing Configure.help text Steven Cole
2001-03-11 6:52 ` Keith Owens
2001-03-11 7:08 ` Jeff Garzik [this message]
2001-03-11 7:20 ` Keith Owens
2001-03-11 13:37 ` Steven Cole
2001-03-11 14:56 ` Keith Owens
2001-04-16 15:06 ` [PATCH] " Jochen Friedrich
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=3AAB245F.A98004D9@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=elenstev@mesatop.com \
--cc=kaos@ocs.com.au \
--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).