From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andreas Dilger <adilger@sun.com>
Cc: Adrian Bunk <bunk@kernel.org>,
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, 2 Jan 2008 20:40:34 +0000 [thread overview]
Message-ID: <20080102204034.703ebdd3@the-village.bc.nu> (raw)
In-Reply-To: <20080102174157.GD3351@webber.adilger.int>
On Wed, 2 Jan 2008 10:41:57 -0700
Andreas Dilger <adilger@sun.com> wrote:
> On Jan 02, 2008 03:32 +0200, Adrian Bunk wrote:
> > It might make sense to offer ext4 in -mm and even in early -rc kernels,
> > but I've already seen people using ext4 simply because a stable kernel
> > offered it - and that's definitely not intended.
> >
> > Anyone who _really_ wants to test ext4 should anyway be able to do the
> > trivial change of removing the "depends on BROKEN" line.
> >
> > Signed-off-by: Adrian Bunk <bunk@kernel.org>
> >
> > @@ -138,7 +138,7 @@ config EXT3_FS_SECURITY
> >
> > config EXT4DEV_FS
> > tristate "Ext4dev/ext4 extended fs support development (EXPERIMENTAL)"
> > - depends on EXPERIMENTAL
> > + depends on BROKEN
> > select JBD2
> > select CRC16
> > help
>
> Isn't CONFIG_EXPERIMENTAL enough?
Of course it is - Adrian is however trying to remove CONFIG_EXPERIMENTAL
and reality is getting in his way again
next prev parent reply other threads:[~2008-01-02 20:50 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
2008-01-02 20:40 ` Alan Cox [this message]
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=20080102204034.703ebdd3@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=adilger@clusterfs.com \
--cc=adilger@sun.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox