From: Adrian Bunk <bunk@kernel.org>
To: linux-kernel@vger.kernel.org
Subject: RFC: remove CONFIG_EXPERIMENTAL
Date: Thu, 1 Nov 2007 06:08:55 +0100 [thread overview]
Message-ID: <20071101050855.GY7227@stusta.de> (raw)
I'm about to send a patch that removes the EXPERIMENTAL option and all
dependencies on EXPERIMENTAL because they are pointless.
Complete rationale:
- Many people and all distributions are currently forced to enable
CONFIG_EXPERIMENTAL since the options for many device drivers depend
on this option.
I have yet to see someone not being able to install his favorite
distribution on his computer only because the distribution did choose
to disable all SATA drivers with dependencies on EXPERIMENTAL in their
kernels...
- History has shown that often the dependency on EXPERIMENTAL is not
removed when the code has proven usable.
As an example, is our NFSv4 support really still in an
"alpha-test phase" [1], or is it already ready for being used?
I don't know the answer in this specific case, but I wouldn't answer
"still in an alpha-test phase" only based on the fact that the NFSv4
options still depend on EXPERIMENTAL.
- It might have been differently 10 years ago, but today everything that
is available in a released kernel should also be in a usable state.
cu
Adrian
[1] quoted from the CONFIG_EXPERIMENTAL help text
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next reply other threads:[~2007-11-01 5:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 5:08 Adrian Bunk [this message]
2007-11-01 8:39 ` RFC: remove CONFIG_EXPERIMENTAL Stefan Richter
2007-11-10 14:33 ` Pierre Ossman
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=20071101050855.GY7227@stusta.de \
--to=bunk@kernel.org \
--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 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.