From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: sam@ravnborg.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC/POC] multiple CONFIG y/m/n
Date: Fri, 7 Apr 2006 14:36:48 -0700 [thread overview]
Message-ID: <20060407143648.137a134d.rdunlap@xenotime.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0604072315530.32445@scrub.home>
On Fri, 7 Apr 2006 23:24:44 +0200 (CEST) Roman Zippel wrote:
> Hi,
>
> On Fri, 7 Apr 2006, Sam Ravnborg wrote:
>
> > > In doing lots of kernel build testing, I often want to enable all options
> > > in a sub-menu and their sub-sub-menus. Sound is one of the worst^W longest
> > > of these, so I chose a shorter (easier) one to practice on: parport.
> > If there is a general need for this we shal enhance kconfig with this.
> > We shall not clutter the Kconfig files with this.
>
> I agree.
> >From a general perspective I still like to add some basic command line
> tool, which can be used for queries or simple manipulations. Here it also
> would be less a problem to add experimental or distribution specific
> functionality instead of overloading conf.c.
> At some point I even had script bindings (via swig), so one could do even
> weirder stuff.
Yep, no problem with Sam's or your reply. Thanks for looking.
---
~Randy
next prev parent reply other threads:[~2006-04-07 21:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-07 5:41 [RFC/POC] multiple CONFIG y/m/n Randy.Dunlap
2006-04-07 15:04 ` OGAWA Hirofumi
2006-04-07 15:45 ` Randy.Dunlap
2006-04-10 5:04 ` Randy.Dunlap
2006-04-12 11:00 ` Roman Zippel
2006-04-12 16:17 ` Randy.Dunlap
2006-04-12 16:59 ` Sam Ravnborg
2006-04-12 18:56 ` [PATCH] config: update usage/help info Randy.Dunlap
2006-04-12 20:44 ` Sam Ravnborg
2006-04-07 18:44 ` [RFC/POC] multiple CONFIG y/m/n Sam Ravnborg
2006-04-07 21:24 ` Roman Zippel
2006-04-07 21:36 ` Randy.Dunlap [this message]
2006-04-11 11:05 ` Jan Engelhardt
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=20060407143648.137a134d.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--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 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.