From: Roman Zippel <zippel@linux-m68k.org>
To: Tomas Szepe <szepe@pinerecords.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] top-level config menu dependencies
Date: Fri, 03 Jan 2003 02:45:42 +0100 [thread overview]
Message-ID: <3E14EB46.21B6AD35@linux-m68k.org> (raw)
In-Reply-To: 20030102195024.GC17053@louise.pinerecords.com
Hi,
Tomas Szepe wrote:
> If I understand you correctly, what you are proposing is equivalent
> to how the following currently works:
>
> config MTD
> tristate "Memory Technology Device (MTD) support"
>
> menu "Memory Technology Device (MTD) support"
> depends on MTD
>
> ...
>
> endmenu
>
> It seems to me the infrastructure you've provided by kconfig
> is completely sufficient -- it's the config frontends that would
> require minor updates (xconfig mainly, menuconfig seems to be
> working nicely -- at least with the setup I outlined above).
Have you tried this with xconfig? What do you mean with "minor updates"?
I don't want to add some special magic, I'd rather make this explicit in
the syntax.
bye, Roman
next prev parent reply other threads:[~2003-01-03 1:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-01 16:25 [RFC] top-level config menu dependencies Tomas Szepe
2003-01-01 16:32 ` John Bradford
2003-01-01 16:42 ` Tomas Szepe
2003-01-02 13:32 ` Roman Zippel
2003-01-02 19:50 ` Tomas Szepe
2003-01-03 1:45 ` Roman Zippel [this message]
2003-01-03 23:46 ` [PATCH] menuconfig support for " Roman Zippel
2003-01-04 4:27 ` Tomas Szepe
2003-01-04 4:53 ` Tomas Szepe
2003-01-04 15:52 ` Menuconfig " Tomas Szepe
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=3E14EB46.21B6AD35@linux-m68k.org \
--to=zippel@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=szepe@pinerecords.com \
--cc=torvalds@transmeta.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 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.