public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Cc: linux-kbuild@vger.kernel.org,
	Filip Honckiewicz <f.honckiewicz@gmail.com>
Subject: Re: Where is the end of "menuconfig" entry scope?
Date: Tue, 18 Jan 2011 11:47:21 +0100	[thread overview]
Message-ID: <4D356FB9.7040807@suse.cz> (raw)
In-Reply-To: <201101172350.26646.yann.morin.1998@anciens.enib.fr>

On 17.1.2011 23:50, Yann E. MORIN wrote:
> Filip, All,
> 
> On Monday 17 January 2011 23:39:17 Filip Honckiewicz wrote:
>> It helped me a lot and now it's clear. Your example shows everything.
>> In kconfig-language.txt there is:
>>  "This is similar to the simple config entry above, but it also gives
>> a hint to front ends, that all suboptions should be displayed as a
>> separate list of options." and this "suboptions" fool me that if
>> there're suboptions than there has to be ending of menuconfig entry;)
> 
> Maybe expressing this in a more understandable way, such as:
> 
>   The menuconfig scope ends with the last config options that depends
>   on that menuconfig entry.

Then such sentence would have to be added to "config" as well. Or just
point people to the Menu structure chapter.

Michal

  reply	other threads:[~2011-01-18 10:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-15 21:35 Where is the end of "menuconfig" entry scope? Filip Honckiewicz
2011-01-17 12:10 ` Michal Marek
2011-01-17 22:39   ` Filip Honckiewicz
2011-01-17 22:50     ` Yann E. MORIN
2011-01-18 10:47       ` Michal Marek [this message]
2011-01-18 14:59         ` Filip Honckiewicz

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=4D356FB9.7040807@suse.cz \
    --to=mmarek@suse.cz \
    --cc=f.honckiewicz@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=yann.morin.1998@anciens.enib.fr \
    /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