From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Adrian Bunk <bunk@kernel.org>
Cc: Diego Calleja <diegocg@gmail.com>,
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:31:16 -0500 [thread overview]
Message-ID: <1199309476.19161.20.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <20080102211655.GC15898@does.not.exist>
On Wed, 2008-01-02 at 23:16 +0200, Adrian Bunk wrote:
> On Wed, Jan 02, 2008 at 07:26:29PM +0100, Diego Calleja wrote:
> > El Wed, 2 Jan 2008 03:32:18 +0200, Adrian Bunk <bunk@kernel.org> escribió:
> >
> > > 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.
> >
> > But isn't that the whole purpose of having ext4 snapshots in the stable kernel - to
> > allow people to try it?
>
> ext4 has quite an unusual development model for kernel code, other
> code in the state of ext4 is usually only in -mm and not in stable
> kernels.
Bullshit... We all do this.
> Stable kernels are mainly meant for usage, not for trying stuff.
> And although I see a point in perhaps shipping some not-yet-perfect
> device drivers for otherwise unsupported hardware or some
> not-yet-perfect filesystems required for accessing foreign
> (non-Linux) filesystems, I don't see any point in offering a
> WIP Linux-only filesystem in stable kernels.
This breaks with the 2.6.x development model that we've been working
with for several years now. I, for one, do not wish to change that
model.
Trond
prev parent reply other threads:[~2008-01-02 21:31 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
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 [this message]
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=1199309476.19161.20.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=adilger@clusterfs.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=diegocg@gmail.com \
--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