From: Eric Sandeen <sandeen@redhat.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: sct@redhat.com, akpm@linux-foundation.org, adilger@clusterfs.com,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6.24 patch] let EXT4DEV_FS depend on BROKEN
Date: Wed, 02 Jan 2008 16:43:23 -0600 [thread overview]
Message-ID: <477C138B.6080803@redhat.com> (raw)
In-Reply-To: <20080102195146.GB15898@does.not.exist>
Adrian Bunk wrote:
> Most people and all distributions use CONFIG_EXPERIMENTAL=y simply
> because too many options (including options required for hardware
> support) depend on it.
>
> Compare e.g.:
> - "Marvell SATA support (HIGHLY EXPERIMENTAL)"
> - "Provide NFSv4 client support (EXPERIMENTAL)"
> - "Ext4dev/ext4 extended fs support development (EXPERIMENTAL)"
tristate "Snapshot target (EXPERIMENTAL)"
depends on BLK_DEV_DM && EXPERIMENTAL
tristate "Mirror target (EXPERIMENTAL)"
depends on BLK_DEV_DM && EXPERIMENTAL
...
It does seem that it might be a good goal to revisit options marked
EXPERIMENTAL, and see if they still should be marked as such, rather
than removing the option altogether.
init/Kconfig describes things in "EXPERIMENTAL" as "alpha-test" - I bet
there are a few things which have moved beyond this, but are still
marked as such.
-Eric
next prev parent reply other threads:[~2008-01-02 22:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-02 1:32 [2.6.24 patch] let EXT4DEV_FS depend on BROKEN Adrian Bunk
2008-01-02 17:41 ` Andreas Dilger
2008-01-02 19:51 ` Adrian Bunk
2008-01-02 21:51 ` Eric Anopolsky
2008-01-04 5:41 ` Valdis.Kletnieks
2008-01-02 22:43 ` Eric Sandeen [this message]
2008-01-02 20:40 ` Alan Cox
2008-01-02 18:26 ` Diego Calleja
2008-01-02 21:16 ` Adrian Bunk
2008-01-02 21:21 ` Alan Cox
2008-01-02 21:31 ` Trond Myklebust
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=477C138B.6080803@redhat.com \
--to=sandeen@redhat.com \
--cc=adilger@clusterfs.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.com \
/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.