From: Carlo Florendo <subscribermail@gmail.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: "menu" versus "menuconfig" -- they're *both* a bad idea
Date: Thu, 12 Apr 2007 09:01:31 +0800 [thread overview]
Message-ID: <461D84EB.7040207@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0704110509200.11343@CPE00045a9c397f-CM001225dbafb6>
Robert P. J. Day wrote:
> (in short, if i, the builder, explicitly choose *not* to add a
> certain feature to my build, i think i have every right to expect that
> some other part of my configuration isn't quietly going to put some
> sub-choice of that feature back in behind my back.)
I agree with this. However, if another feature actually depends on another
explicitly unselected feature, there should at least be a warning prompt
that such is the case.
It probably would be hard though to track all dependencies.
Best Regards,
Carlo
--
Carlo Florendo
Softare Engineer/Network Co-Administrator
Astra Philippines Inc.
UP-Ayala Technopark, Diliman 1101, Quezon City
Philippines
http://www.astra.ph
--
The Astra Group of Companies
5-3-11 Sekido, Tama City
Tokyo 206-0011, Japan
http://www.astra.co.jp
next prev parent reply other threads:[~2007-04-12 1:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 7:58 "menu" versus "menuconfig" -- they're *both* a bad idea Robert P. J. Day
2007-04-11 9:06 ` Jan Engelhardt
2007-04-11 9:25 ` Robert P. J. Day
2007-04-11 9:35 ` Jan Engelhardt
2007-04-11 9:47 ` Robert P. J. Day
2007-04-11 15:43 ` Jan Engelhardt
2007-04-11 16:00 ` Robert P. J. Day
2007-04-12 1:01 ` Carlo Florendo [this message]
2007-04-12 7:24 ` DervishD
2007-04-12 15:21 ` Robert P. J. Day
2007-04-12 18:54 ` Stefan Richter
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=461D84EB.7040207@gmail.com \
--to=subscribermail@gmail.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.com \
/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