From: DervishD <lkml@dervishd.net>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: introducing conditional submenus in the config process?
Date: Fri, 9 Feb 2007 15:51:22 +0100 [thread overview]
Message-ID: <20070209145122.GA11820@DervishD> (raw)
In-Reply-To: <Pine.LNX.4.64.0702090901500.5499@localhost.localdomain>
Hi Robert :)
* Robert P. J. Day <rpjday@mindspring.com> dixit:
>
> i brought this up a while back but nothing was finalized -- is there
> sufficient value in being able to select or deselect entire submenus
> of features without having to descend into that submenu first?
Not that my opinion counts at all, but IMHO this is a VERY good
idea. OK, the kernel configuration system is not for the faint of heart
anyway, but doing it a bit more user-friendly is a good idea.
Apart for user-friendlyness, which in itself is a good point, the
most important thing here is speed. Normally I have a base .config and I
work by adding/removing a couple of features, but being able to
deselect/select full submenus in just one checkbox is faster (and IMHO
less error prone, specially when your fingers fly across the keyboard)
than having to descend.
Moreover, it adds a bit more of structure to the kernel
configuration. The first time it can be scary...
So, I vote for that, even if my opinion doesn't count and I don't
have a vote. For me looks like a very good idea.
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!
prev parent reply other threads:[~2007-02-10 10:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 14:10 introducing conditional submenus in the config process? Robert P. J. Day
2007-02-09 14:51 ` DervishD [this message]
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=20070209145122.GA11820@DervishD \
--to=lkml@dervishd.net \
--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