From: Tomas Szepe <szepe@pinerecords.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [TRIVIAL] kill annoying submenus in fs/Kconfig
Date: Sun, 27 Jul 2003 09:02:52 +0200 [thread overview]
Message-ID: <20030727070252.GD17724@louise.pinerecords.com> (raw)
In-Reply-To: <20030726200903.73d17418.rddunlap@osdl.org>
> [rddunlap@osdl.org]
>
> On Sat, 26 Jul 2003 21:55:44 +0200 Tomas Szepe <szepe@pinerecords.com> wrote:
>
> | Patch against -bk3.
>
> Let me begin by saying that I find the menu arrangement (both before
> and after this patch) highly subjective.
I guess so.
> I.e., there's not necessarily a right or wrong. (RR:)
> I.e., in the absence of further input, some maintainer can decide. :)
>
> Given the above:
> I prefer short menus. I find them more readable, with less clutter.
> So I don't mind them the way that they currently are.
>
> OTOH, I don't care strongly either way. I think that we should
> care more about how non-developers use and see 'make *config'
> than how kernel developers use and see it.
I can't see why we need to categorize ~50 (that is _two_ 80x25 screenfuls)
filesystems into 7 or so submenus. The going back and forth in menuconfig
just to check if NFS and proc are enabled for a basic config is highly
annoying IMHO. The categorization itself is a nice idea, though.
--
Tomas Szepe <szepe@pinerecords.com>
next prev parent reply other threads:[~2003-07-27 6:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-26 19:55 [TRIVIAL] kill annoying submenus in fs/Kconfig Tomas Szepe
2003-07-27 3:09 ` Randy.Dunlap
2003-07-27 7:02 ` Tomas Szepe [this message]
2003-08-05 7:27 Tomas Szepe
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=20030727070252.GD17724@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=torvalds@osdl.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).