From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][RFC] Create a top-level "Space-critical features" menu.
Date: Tue, 8 May 2007 12:19:05 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0705081215220.8750@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61.0705081117051.17280@yvahk01.tjqt.qr>
On Tue, 8 May 2007, Jan Engelhardt wrote:
>
> On May 8 2007 04:41, Robert P. J. Day wrote:
> >
> > in my opinion, the config option "EMBEDDED" is just plain silly. as
> >i mentioned earlier, there may be other reasons that people want to
> >de-activate normally selected features rather than just for strictly
> >embedded systems.
>
> Did not you want to make a patch row that expresses all your ideas, aka
> CONFIG_EXPERT
> CONFIG_ASKFORDETAILS (former CONFIG_EMBEDDED, e.g. "place in memory where
> kernel is loaded")
> CONFIG_OBSOLETE
> CONFIG_DEPRECATED
> etc.? :)
i hadn't actually considered *that* possibility, but the idea is sort
of what i had in mind -- a clear, top-level setting that, in one swell
foop, will change what's available throughout the tree. i think
that's the most intuitively clear way to do it.
rday
p.s. mostly, i just don't think labelling that selection with the
word "EMBEDDED" makes a lot of sense. who's to say that any given
feature should be de-selectable only on an embedded system?
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
next prev parent reply other threads:[~2007-05-08 16:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 8:06 Robert P. J. Day
2007-05-08 8:21 ` Thomas Gleixner
2007-05-08 8:27 ` Robert P. J. Day
2007-05-08 8:37 ` Thomas Gleixner
2007-05-08 8:41 ` Robert P. J. Day
2007-05-08 9:21 ` Jan Engelhardt
2007-05-08 13:03 ` Stefan Richter
2007-05-08 16:19 ` Robert P. J. Day [this message]
2007-05-08 20:22 ` Matt Mackall
2007-05-08 8:56 ` Adrian Bunk
2007-05-08 16:14 ` Robert P. J. Day
2007-05-08 20:10 ` Matt Mackall
2007-05-08 20:34 ` Robert P. J. Day
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=Pine.LNX.4.64.0705081215220.8750@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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®