From: Michal Marek <mmarek@suse.cz>
To: Peter Korsgaard <jacmet@sunsite.dk>
Cc: nir.tzachar@gmail.com, sam@ravnborg.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] nconf: handle comment entries within choice/endchoice
Date: Fri, 7 Jan 2011 16:02:21 +0100 [thread overview]
Message-ID: <20110107150221.GD1841@sepie.suse.cz> (raw)
In-Reply-To: <1294328565-2750-1-git-send-email-jacmet@sunsite.dk>
On Thu, Jan 06, 2011 at 04:42:45PM +0100, Peter Korsgaard wrote:
> Equivalent to af6c1598 (kconfig: handle comment entries within
> choice/endchoice), but for nconfig instead.
>
> Implement support for comment entries within choice groups. Comment entries
> are displayed visually distinct from normal configs, and selecting them is
> a no-op.
>
> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
> ---
> scripts/kconfig/nconf.c | 8 ++++++--
> 1 files changed, 6 insertions(+), 2 deletions(-)
OK, applied, but is this actually used somewhere?
Michal
next prev parent reply other threads:[~2011-01-07 15:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 15:42 [PATCH] nconf: handle comment entries within choice/endchoice Peter Korsgaard
2011-01-07 15:02 ` Michal Marek [this message]
2011-01-07 22:32 ` Peter Korsgaard
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=20110107150221.GD1841@sepie.suse.cz \
--to=mmarek@suse.cz \
--cc=jacmet@sunsite.dk \
--cc=linux-kbuild@vger.kernel.org \
--cc=nir.tzachar@gmail.com \
--cc=sam@ravnborg.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