From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
kbuild-devel@lists.sourceforge.net,
Andreas Herrmann <aherrman@arcor.de>,
Eric Van Hensbergen <ericvh@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 9p: fix compile error if !CONFIG_SYSCTL
Date: Fri, 28 Sep 2007 10:05:33 +1000 [thread overview]
Message-ID: <200709281005.34001.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <alpine.LFD.0.999.0709280728170.3579@woody.linux-foundation.org>
On Saturday 29 September 2007 00:34, Linus Torvalds wrote:
> On Fri, 28 Sep 2007, Nick Piggin wrote:
> > > God I hate select.
> >
> > IMO a better implementation would result in a notification / confirmation
> > of turning on new items, and the ability to deselect options which will
> > also confirm to deselect dependants. Like most other systems that have
> > similar problem to solve.
>
> Actually, the *really* nice thing to do would be to just add the reason
> something got enabled into the ".config" file.
>
> IOW, wouldn't it be nice if the .config file just said
>
> ...
> CONFIG_ACPI=y # selected by X86_64_ACPI_NUMA
> CONFIG_ACPI_PROCFS=y # user choice
> ...
>
> etc, since the config process actually does know these things?
Sure, that would probably be pretty trivial to implement too, and
would solve most problems for kernel devs.
At a level up from that, I think ease of use could be improved with
a package manager-type chained-selection/deselection feature in
the config tools.
Not that I'm volunteering to implement either ;)
>
> That way, there's always a fairly straightforward way to see why some
> configuration is the way it is (and the .config file is not only useful
> for "make oldconfig", it's also what normally gets passed around for bug
> reports, and is part of distro kernel packages etc, so it would seem to be
> the right place, no?)
>
> Linus
next prev parent reply other threads:[~2007-09-28 16:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 8:05 Andreas Herrmann
2007-09-18 18:53 ` roel
2007-09-18 20:15 ` Andreas Herrmann
2007-09-20 6:31 ` Andrew Morton
2007-09-20 7:23 ` Andreas Herrmann
2007-09-27 21:40 ` Nick Piggin
2007-09-28 14:34 ` Linus Torvalds
2007-09-28 0:05 ` Nick Piggin [this message]
2007-09-28 17:11 ` Arjan van de Ven
2007-09-28 17:12 ` Elyse M. Grasso
2007-10-01 7:27 ` A bit of kconfig rewrite (Re: [PATCH] 9p: fix compile error if !CONFIG_SYSCTL) Oleg Verych
2007-10-01 8:05 ` Sam Ravnborg
2007-10-01 12:53 ` Elyse M. Grasso
2007-10-05 2:35 ` [kbuild-devel] " Roman Zippel
2007-10-06 15:26 ` Oleg Verych
2007-10-06 16:03 ` Linus Torvalds
2007-10-06 17:51 ` Oleg Verych
2007-10-06 18:59 ` Sam Ravnborg
2007-10-06 20:47 ` Oleg Verych
2007-10-06 21:10 ` Sam Ravnborg
2007-10-06 22:07 ` Oleg Verych
2007-10-07 9:49 ` Geert Uytterhoeven
2007-10-08 20:22 ` Sam Ravnborg
2007-10-08 21:25 ` Oleg Verych
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=200709281005.34001.nickpiggin@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=aherrman@arcor.de \
--cc=akpm@linux-foundation.org \
--cc=ericvh@gmail.com \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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®