From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org, sam@ravnborg.org
Subject: Re: [PATCH 0/19] kconfig patches
Date: Wed, 19 Apr 2006 20:51:41 -0700 [thread overview]
Message-ID: <20060419205141.63298a26.rdunlap@xenotime.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0604091628240.21970@scrub.home>
On Sun, 9 Apr 2006 17:26:16 +0200 (CEST) Roman Zippel wrote:
> Hi,
>
> Here is a batch of kconfig (and also some kbuild related) patches. The
> first four patches I'd like to see to go into 2.6.17 if possible. Although
> I'm quite confident about the remaining patches, a bit more testing can't
> hurt.
>
> Some comments about the most interesting aspects from a user perspective
> for these patches:
>
> Now it's possible to do something like "vi .config; make" and be
> reasonably certain it does the right thing, before especially kbuild
> related config changes were not correctly picked up by make and required
> an explicit "make oldconfig".
[snip]
> Another interesting feature are the xconfig changes, it supports now a
> search option like menuconfig and the help output links to other symbols,
> so one can basically browse through the kconfig info. The latter is still
> a bit experimental, so it's only visible if the debug info option is
> enabled.
Hi Roman,
I have a few questions about this patch series. All of them are
about using *config (i.e., this is not a patch review).
~~~~~
Subject: [PATCH 12/19] kconfig: add symbol option config syntax
Do we have any examples of this? (where)
~~~~~
Subject: [PATCH 14/19] kconfig: Add search option for xconfig
How do I search? I don't see it in the menu or any Help for it.
~~~~~
Subject: [PATCH 15/19] kconfig: finer customization via popup menus
How? documentation?
~~~~~
Subject: [PATCH 16/19] kconfig: create links in info window
How? what does link look like? are there any in the current
Kconfig menus? I'd like to see one (or several).
~~~~~
Subject: [PATCH 17/19] kconfig: jump to linked menu prompt
I'd like to see this too. Where can I see it?
~~~~~
Thanks,
---
~Randy
next prev parent reply other threads:[~2006-04-20 3:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-09 15:26 Roman Zippel
2006-04-10 6:55 ` Andrew Morton
2006-04-10 8:46 ` Roman Zippel
2006-04-10 7:51 ` Andrew Morton
2006-04-10 9:35 ` Roman Zippel
2006-04-10 8:41 ` Andrew Morton
2006-04-10 11:36 ` Roman Zippel
2006-04-10 15:22 ` Randy.Dunlap
2006-04-10 21:24 ` Andrew Morton
2006-04-12 10:51 ` Roman Zippel
2006-04-20 3:51 ` Randy.Dunlap [this message]
2006-04-26 22:13 ` Roman Zippel
2006-04-26 22:38 ` Randy.Dunlap
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=20060419205141.63298a26.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®