From: Helge Hafting <helgehaf@aitel.hist.no>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: a really annoying feature of the config menu structure
Date: Wed, 19 Feb 2003 14:19:53 +0100 [thread overview]
Message-ID: <3E538479.1040305@aitel.hist.no> (raw)
In-Reply-To: <Pine.LNX.4.44.0302181604310.23007-100000@dell>
Robert P. J. Day wrote:
> i finally decided to get serious and start looking at the
> overall config menu structure, to re-arrange the menus and
> submenus so that it made more sense and flowed more logically,
[...]
> other areas where this would have made sense would be for
> something like a "Networking" main menu, with submenus for
> things like ISDN, Wireless and so on, those all being
> subsets of networking.
It isn't that simple. ISDN is more than networking, and even
useable without it. Non-network uses of isdn:
* Making an answering machine or voicemail from a pc
and one or more isdn cards.
* Use isdn for dialing into non-IP services like a BBS.
So you have a choice between sticking all networking
things in a network menu (and have stuff like ISDN
spread out in different places (network and other ISDN at least)
or put all ISDN in one plave and have network etc. spread over
various networking technologies like today.
There is no config layout that is "clean" for everybody,
because it is fundamentally trying to stuff a generic graph
into a hierarchical tree.
Helge Hafting
next prev parent reply other threads:[~2003-02-19 13:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 21:28 Robert P. J. Day
2003-02-18 22:33 ` Stephen Wille Padnos
2003-02-19 1:04 ` Robert P. J. Day
2003-02-19 1:24 ` Stephen Wille Padnos
2003-02-19 2:09 ` Robert P. J. Day
2003-02-19 1:56 ` Alan Cox
2003-02-19 1:31 ` Stephen Wille Padnos
2003-02-19 3:03 ` Alan Cox
2003-02-19 2:13 ` Robert P. J. Day
2003-02-19 9:49 ` Tomas Szepe
2003-02-19 13:19 ` Helge Hafting [this message]
2003-02-19 13:31 ` Robert P. J. Day
2003-02-19 14:35 ` John Bradford
2003-02-19 13:33 ` Robert P. J. Day
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=3E538479.1040305@aitel.hist.no \
--to=helgehaf@aitel.hist.no \
--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
all inboxes | Powered by JetHome®