mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Chris Mason <chris.mason@oracle.com>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Btrfs mainline plans
Date: Sun, 5 Oct 2008 15:24:05 +0300	[thread overview]
Message-ID: <20081005122405.GA12047@cs181140183.pp.htv.fi> (raw)
In-Reply-To: <20081003001859.e30af6a5.akpm@linux-foundation.org>

On Fri, Oct 03, 2008 at 12:18:59AM -0700, Andrew Morton wrote:
> On Mon, 29 Sep 2008 15:44:20 -0400 Chris Mason <chris.mason@oracle.com> wrote:
> 
> > But, the code is very actively developed, and I believe the best way to
> > develop Btrfs from here is to get it into the mainline kernel (with a
> > large warning label about the disk format) and attract more extensive
> > review of both the disk format and underlying code.
> 
> For the record...  I have been encouraging Chris to get btrfs into
> mainline soon.  Get it into linux-next asap and merge it into 2.6.29.
> 
> And do this even though the on-disk format is still changing - we emit a
> loud printk at mount time and if someone comes to depend upon some
> intermediate format, well, that's their tough luck.
> 
> My thinking here is that btrfs probably has a future, and that an early
> merge will accelerate its development and will broaden its developer base. 
> If it ends up failing for some reason, well, we can just delete it
> again.
> 
> For various reasons this approach often isn't appropriate as a general
> policy thing, but I do think that Linux has needed a new local
> filesystem for some time, and btrfs might be The One, and hence is
> worth a bit of special-case treatment.

Let's try to learn from the past:

6 days from today ext4 (another new local filesystem for Linux) 
celebrates the second birthday of it's inclusion into Linus' tree
as a similar special-case.

You claim "an early merge will accelerate its development and will 
broaden its developer base" for Btrfs.

Read the timeline Ted outlined back in June 2006 for ext4 [1].
When comparing with what happened in reality it kinda disproves
your "acceleration" point.

cu
Adrian

[1] http://lkml.org/lkml/2006/6/28/454

-- 

       "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-05 12:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-29 19:44 Chris Mason
2008-10-03  7:18 ` Andrew Morton
2008-10-05 12:24   ` Adrian Bunk [this message]
2008-10-05 14:11     ` Serge E. Hallyn
2008-10-05 15:09       ` 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-07 21:20                 ` David Sanders
2008-10-07 21:27                   ` Randy.Dunlap
2008-10-08 12:53                   ` Christoph Hellwig
2008-10-08 17:48                     ` David Sanders
2008-10-08 21:33         ` Daniel Phillips
2008-10-09  8:22           ` Adrian Bunk
2008-10-10  3:01             ` Theodore Tso
2008-10-03 17:06 ` Jan Engelhardt

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=20081005122405.GA12047@cs181140183.pp.htv.fi \
    --to=bunk@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=chris.mason@oracle.com \
    --cc=linux-fsdevel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®