public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: more thoughts on kernel config organization
Date: Sun, 12 Jan 2003 18:12:19 +0100	[thread overview]
Message-ID: <3E21A1F3.8E65FC93@linux-m68k.org> (raw)
In-Reply-To: Pine.LNX.4.44.0301112300570.20815-100000@dell

Hi,

"Robert P. J. Day" wrote:

>   also, there are at least a couple places in that xconfig
> meny that seem incorrectly-structured.  example: ext3 -> JBD.
> JBD is a sub-option of ext3, but it shows up at the same
> indentation level.  it should, based on hierarchy, be one
> level indented, at the same level as ext3 extended attributes
> to be a proper sub-option.
> 
>   same complaint about VFAT being a sub-option of DOS FAT fs
> support, but not being indented properly.

You always have to remember that the dependency information is used to
generate the menu structure. If you enable "Show All Options" in
xconfig, you can easily find out what's preventing a correct menu
structure. E.g. for VFAT you have two possibilities, move down the
UMSDOS_FS entry or add "depends on FAT_FS" to it.
If you want one config entry to appear as a child of another entry, it
must have at least that other entry in its dependency list.

bye, Roman



  parent reply	other threads:[~2003-01-12 17:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-12  4:17 more thoughts on kernel config organization Robert P. J. Day
2003-01-12  8:04 ` Sam Ravnborg
2003-01-12  9:22   ` Robert P. J. Day
2003-01-12 10:03     ` Tomas Szepe
2003-01-12 17:12 ` Roman Zippel [this message]
2003-01-13 12:32 ` Dave Jones

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=3E21A1F3.8E65FC93@linux-m68k.org \
    --to=zippel@linux-m68k.org \
    --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