public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Daniel Phillips <phillips@phunq.net>
Cc: "Serge E. Hallyn" <serue@us.ibm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Chris Mason <chris.mason@oracle.com>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-ext4@vger.kernel.org, Theodore Tso <tytso@mit.edu>
Subject: Re: [RFC] Btrfs mainline plans
Date: Thu, 9 Oct 2008 11:22:34 +0300	[thread overview]
Message-ID: <20081009082234.GA17013@cs181140183.pp.htv.fi> (raw)
In-Reply-To: <200810081433.32766.phillips@phunq.net>

On Wed, Oct 08, 2008 at 02:33:32PM -0700, Daniel Phillips wrote:
> On Sunday 05 October 2008 08:09, Adrian Bunk wrote:
> > "accelerate its development and will broaden its developer base" is not 
> > about users/testers but about people doing code development.
> > 
> > For people wanting to try WIP code you don't need it in mainline.
> 
> But it saves time for the user, who does not have to run around chasing
> links, carefully checking for a kernel match, downloading, patching,
> building and installing a single purpose kernel, and bringing it up on
> a machine that would probably have only required one click on the new
> filesystem option otherwise.  The considerable time thus saved can be
> invested profitably in running test cases and filing bug reports.

Bug reports against a 3-6 months old snapshot of a filesystem being 
under heavy development.

Ted said back in August in the announcement of an ext4 patchset:

"As before I've also released updated the patch set vs. the 2.6.26 stock
 kernel, for those people who don't want to play with development 
 kernels but who still want to test out ext4." [1]

When running stable kernels you still have to patch, build and install
a single purpose kernel for testing ext4 although ext4 is in mainline.

>...
> > This is not meant as a statement on the quality of ext4 or btrfs, or any 
> > comparison of the development times of ext4 and btrfs, but for ext4 the 
> > advantages Andrew thinks would happen with an early btrfs merge do not 
> > seem to have happened.
> 
> Are you sure about that?  I see 33 messages on linux-ext4 yesterday,
> from a broad range of contributors.  Versus eight from a much narrower
> range of contributors, Oct 4 a year ago.

There are lies, damn lies, and statistics.  ;)

Single day statistics about mailing list postings are not very good
indicators for anything.

And since linux-ext4 is for all of ext2/ext3/ext4 the data you gave 
could equally be used to prove that ext3 recently became much more
buggy or that ext2 development vastly increased...

> There is little question that an early merge helps both developers and
> users employ their time more efficiently,

Regarding users see my comment above.

Regarding developers it would be interesting to hear some experiences 
from ext4 developers about their experiences (or get a pointer to them 
in case I missed that they already expressed it somewhere).

> once a project is past the
> point where we wonder about its value and/or viability.  In my opinion,
> Btrfs clearly has both.
>...

2 years ago ext4 was in a similar situation of being regarded as an 
important future filesystem.

> Regards,
> 
> Daniel

cu
Adrian

BTW: My comments are not in any way meant against btrfs or ext4.
     I just question the advantages of merging them early.


[1] http://lwn.net/Articles/294784/

-- 

       "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


  reply	other threads:[~2008-10-09  8:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1222717460.30627.56.camel@think.oraclecorp.com>
     [not found] ` <20081003001859.e30af6a5.akpm@linux-foundation.org>
     [not found]   ` <20081005122405.GA12047@cs181140183.pp.htv.fi>
     [not found]     ` <20081005141113.GA6132@us.ibm.com>
2008-10-05 15:09       ` [RFC] Btrfs mainline plans Adrian Bunk
2008-10-06 13:40         ` Chris Mason
2008-10-07 15:27           ` Adrian Bunk
2008-10-07 16:01             ` Chris Mason
2008-10-07 20:25               ` Adrian Bunk
2008-10-08 21:33         ` Daniel Phillips
2008-10-09  8:22           ` Adrian Bunk [this message]
2008-10-10  3:01             ` Theodore Tso

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=20081009082234.GA17013@cs181140183.pp.htv.fi \
    --to=bunk@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=chris.mason@oracle.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@phunq.net \
    --cc=serue@us.ibm.com \
    --cc=tytso@mit.edu \
    /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