From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.5.68 FUTEX support should be optional
Date: Thu, 15 May 2003 00:59:47 +0200 [thread overview]
Message-ID: <3EC2CA63.6030301@gmx.net> (raw)
In-Reply-To: <200305141829_MC3-1-38F1-59C7@compuserve.com>
Chuck Ebbert wrote:
> hpa wrote:
>
>
>>How about creating a master option like we have for experimental?
>>Something like "Allow removal of essential components?" (CONFIG_EMBEDDED)
>
>
> ...and that just enables another option: "REALLY allow removal of
> essential components?" (CONFIG_REALLY_EMBEDDED)
>
> :)
Reminds me of CONFIG_MORON back in December 2000
-dep_mbool ' NTFS write support (DANGEROUS)' CONFIG_NTFS_RW
$CONFIG_NTFS_FS $CONFIG_EXPERIMENTAL
+dep_mbool ' NTFS write support (DANGEROUS)' CONFIG_MORON
$CONFIG_NTFS_FS $CONFIG_EXPERIMENTAL
+dep_bool ' Are you sure? I hope you dont care about your NTFS
filesystems' CONFIG_NTFS_RW $CONFIG_MORON
;)
Carl-Daniel
--
And the mailer looked at the patch and, behold, it was good. And the
mailer decided to wrap the patch.
next prev parent reply other threads:[~2003-05-14 22:47 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 22:26 [PATCH] 2.5.68 FUTEX support should be optional Chuck Ebbert
2003-05-14 22:59 ` Carl-Daniel Hailfinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-14 23:33 Perez-Gonzalez, Inaky
2003-05-15 0:41 ` Andrew Morton
2003-05-15 0:52 ` Christopher Hoover
2003-05-15 1:00 ` Linus Torvalds
2003-05-15 1:25 ` Andrew Morton
2003-05-15 1:28 ` Linus Torvalds
2003-05-15 1:39 ` Andrew Morton
2003-05-15 1:42 ` Davide Libenzi
2003-05-15 2:02 ` Christopher Hoover
2003-05-15 2:18 ` Davide Libenzi
2003-05-15 3:01 ` Arnaldo Carvalho de Melo
2003-05-15 3:45 ` Linus Torvalds
2003-05-15 18:14 ` Bill Davidsen
2003-05-16 21:55 ` Alan Cox
2003-05-17 0:01 ` Valdis.Kletnieks
2003-05-17 2:36 ` Andrew Morton
2003-05-17 9:40 ` Werner Almesberger
2003-05-14 4:32 Christopher Hoover
2003-05-14 6:14 ` Christoph Hellwig
2003-05-14 6:20 ` Miles Bader
2003-05-14 6:28 ` Christoph Hellwig
2003-05-14 6:32 ` Andrew Morton
2003-05-14 6:35 ` Christoph Hellwig
2003-05-14 7:52 ` Christopher Hoover
2003-05-14 19:19 ` Ulrich Drepper
2003-05-14 19:32 ` Dave Jones
2003-05-14 19:44 ` Ulrich Drepper
2003-05-14 19:50 ` Linus Torvalds
2003-05-14 20:01 ` Andrew Morton
2003-05-14 20:43 ` Davide Libenzi
2003-05-14 20:54 ` H. Peter Anvin
2003-05-14 21:05 ` Davide Libenzi
2003-05-15 0:58 ` Christopher Hoover
2003-05-15 1:20 ` Linus Torvalds
2003-05-15 2:18 ` Miles Bader
2003-05-15 16:47 ` Ingo Oeser
2003-05-15 17:45 ` Ulrich Drepper
2003-05-15 18:00 ` Bill Davidsen
2003-05-15 18:16 ` Ulrich Drepper
2003-05-15 18:04 ` Christopher Hoover
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=3EC2CA63.6030301@gmx.net \
--to=c-d.hailfinger.kernel.2003@gmx.net \
--cc=76306.1226@compuserve.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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