From: Adrian Bunk <bunk@fs.tum.de>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] new kconfig goodies
Date: Mon, 12 May 2003 16:16:20 +0200 [thread overview]
Message-ID: <20030512141619.GO1107@fs.tum.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0305111838300.14274-100000@serv>
On Mon, May 12, 2003 at 03:39:11PM +0200, Roman Zippel wrote:
> Hi,
Hi Roman,
>...
> BTW this clears my todo list of important features for the kconfig syntax
> itself, if you think there is something missing, please tell me now,
> otherwise it might have to wait for 2.7. After this I work a bit more on
> xconfig and the library interface.
>...
there's one feature I'd like to see (I don't see an easy way to achieve
it currently):
A choice with the possibility to select one or more entries, to support
things like:
Supported processors:
[ ] 386
[ ] 486
[ ] 586
...
It should be possible to select more than one item but selecting zero
items should be illegal.
> bye, Roman
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2003-05-12 14:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 13:39 [PATCH] new kconfig goodies Roman Zippel
2003-05-12 14:16 ` Adrian Bunk [this message]
2003-05-12 15:37 ` Roman Zippel
2003-05-12 14:32 ` Dave Jones
2003-05-12 15:39 ` Roman Zippel
2003-05-12 16:08 ` Dave Jones
2003-05-12 16:00 ` Tomas Szepe
2003-05-12 22:36 ` Roman Zippel
2003-05-12 15:13 ` Geert Uytterhoeven
2003-05-12 15:43 ` Roman Zippel
2003-05-13 1:38 ` Miles Bader
2003-05-13 1:44 ` Miles Bader
2003-05-13 15:27 ` Roman Zippel
2003-05-13 21:17 ` Miles Bader
2003-05-14 19:51 ` Roman Zippel
2003-05-14 20:56 ` Andreas Schwab
2003-05-14 22:11 ` Roman Zippel
2003-05-15 0:21 ` Michael Alan Dorman
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=20030512141619.GO1107@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.