From: Paul Bolle <pebolle@tiscali.nl>
To: Jan Beulich <JBeulich@suse.com>
Cc: akpm@linux-foundation.org, Michal Marek <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Kconfig: drop bogus default values
Date: Thu, 12 Mar 2015 13:11:47 +0100 [thread overview]
Message-ID: <1426162307.5304.41.camel@x220> (raw)
In-Reply-To: <5500584D02000078000688F5@mail.emea.novell.com>
[Removed Yann.]
On Wed, 2015-03-11 at 13:59 +0000, Jan Beulich wrote:
> Default "no" is pretty pointless for options without (visible) prompts:
Related: is there ever a situation where using "default n" or "def_bool
n" makes sense (whether or not the entry has a prompt)? I think I once
thought of one but I can't remember it at all, so I guess my memory is
fooling me.
> They only clutter .config-s with "# CONFIG_... is not set" and thus
As far as I can see the main effect of using "default n" is that this
line will be printed.
> prevent users of "make oldconfig", when the option obtains a prompt or
> its prompt becomes visible, noticing that these may now be enabled.
This side effect doesn't look like a feature. I scanned the source a bit
but - as usual - didn't stumble on a comment that might explain this
behavior. Michal probably feels better at home in the code and might be
able to offer a rationale.
Paul Bolle
next prev parent reply other threads:[~2015-03-12 12:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 13:59 [PATCH] Kconfig: drop bogus default values Jan Beulich
2015-03-11 13:59 ` Jan Beulich
2015-03-12 12:11 ` Paul Bolle [this message]
2015-03-12 12:36 ` Jan Beulich
2015-03-12 12:36 ` Jan Beulich
2015-03-12 12:41 ` Paul Bolle
2015-03-12 18:51 ` Sam Ravnborg
2015-03-23 21:08 ` Martin Walch
2015-03-23 21:24 ` Paul Bolle
2015-03-23 22:58 ` Martin Walch
2015-03-24 7:39 ` Jan Beulich
2015-03-24 7:39 ` Jan Beulich
2015-03-24 7:38 ` Jan Beulich
2015-03-24 7:38 ` Jan Beulich
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=1426162307.5304.41.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=JBeulich@suse.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.