public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Ramsey <MikeJRamsey@comcast.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Release plan
Date: Wed, 24 Jun 2009 01:11:24 +0000 (UTC)	[thread overview]
Message-ID: <loom.20090624T010114-686@post.gmane.org> (raw)
In-Reply-To: f058a9c30906230309y316920e1he31ab3bdb467c311@mail.gmail.com

Miguel F Mascarenhas Sousa Filipe <miguel.filipe <at> gmail.com> writes:

[snip]
> 
> You mean ZFS, but I think everybody who read this "self-corrected" your typo.

Yes, I mean ZFS.  ZFS used to be known as the Zettapoint File System.  
I guess my subconsciousness couldn't let go of the "point".
 
[snip]
> 
> File systems take a long time to mature, btrfs is stable enough for
> daily use, has long has you don't use it for sensitive/critical data.
> There are still some problems, the most annoying being the premature
> "out of space"/"disc full" errors.
> I would say that in time for Fedora 12, you will probably have a btrfs
> more usable for the common user, but still not advised for the faint
> of heart.
> 
> Consider the time that ext4 took to mature and for people to trust it.
> Ext4 is stable for quite some months, but even now, the majority of
> recent distro builds choose ext3 has the default file system.
> 
> Again.. file systems take quite a bit of time to mature...
[snip]

I know.  A schedule has an amazing way of focusing people on what is 
important.  There may be ten things that should be done but not all ten 
things  need to be done.  :-)

--Best regards,
--Mike Ramsey





  reply	other threads:[~2009-06-24  1:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 15:53 Release plan Mike Ramsey
     [not found] ` <f058a9c30906230308m2062bbdbs519d65389400e39e@mail.gmail.com>
2009-06-23 10:09   ` Miguel F Mascarenhas Sousa Filipe
2009-06-24  1:11     ` Mike Ramsey [this message]
2009-06-25 22:38       ` Valerie Aurora
2009-06-26  1:38         ` Mike Ramsey

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=loom.20090624T010114-686@post.gmane.org \
    --to=mikejramsey@comcast.net \
    --cc=linux-btrfs@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