From: "Randy.Dunlap" <randy.dunlap@verizon.net>
To: linux-kernel@vger.kernel.org, rpjday@mindspring.com
Subject: Re: restructuring of filesystems config menu
Date: Sat, 25 Jan 2003 15:15:46 -0800 [thread overview]
Message-ID: <3E331AA2.38F99839@verizon.net> (raw)
In-Reply-To: Pine.LNX.4.33L2.0301132030590.2674-101000@dragon.pdx.osdl.net
Hi,
> Date: Sun, 12 Jan 2003 07:57:33 -0500 (EST)
> From: Robert P. J. Day <rpjday@mindspring.com>
> Subject: restructuring of filesystems config menu
>
> i've attached a gzipped patch against 2.5.56 for reorganizing
> the filesystem menu under "make xconfig", and i'm certainly
> open to feedback/comments/criticism/large sums of money.
Good luck with those. :)
I finally looked at this on 2.5.59. The fs menu certainly
needs some help/work, so I'd like to see you keep plugging away
at this. I didn't see much feedback -- was there feedback?
Maybe on a different subject/thread? A newer version that I
missed?
> some points about this patch:
>
> 1) if anyone wants to carefully check the dependencies and
> make sure they're correct, that would be nice.
>
> 2) perhaps making sure the dependencies match the claims
> in the help screens would be helpful. i noticed that
> the help screens sometimes make dependency claims that
> are wildly untrue, but i didn't want to mess with that
> stuff yet as i wasn't totally comfortable.
>
> 3) much to my delight, i found out by accident that i can
> add leading asterisks to menu and config lines with no
> effect on the eventual config step -- this makes it
> wonderfully easy to edit and reorganize using emacs
> outline mode, particularly showing subdependencies.
I find it odd that "help" in a Kconfig file can be spelled
"help" or "---help---", but "--help--" leads to errors.
> is this just a fluke? obviously, it's easy enough to
> strip out the leading asterisks in the final version,
> but if they're not doing any harm, i'd just as soon
> leave them in.
I expected to just see the filesystems listed in alpha order,
but I don't have a problem with the groupings that you
have made for them.
Thanks,
~Randy
next parent reply other threads:[~2003-01-25 23:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33L2.0301132030590.2674-101000@dragon.pdx.osdl.net>
2003-01-25 23:15 ` Randy.Dunlap [this message]
2003-01-26 10:05 ` restructuring of filesystems config menu Robert P. J. Day
2003-01-27 0:25 ` Randy.Dunlap
2003-01-12 12:57 Robert P. J. Day
2003-01-13 0:01 ` Randy Dunlap
2003-01-13 0:42 ` 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=3E331AA2.38F99839@verizon.net \
--to=randy.dunlap@verizon.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