From: Mike Ramsey <michael.j.ramsey@lmco.com>
To: linux-btrfs@vger.kernel.org
Subject: Release plan
Date: Mon, 22 Jun 2009 15:53:02 +0000 (UTC) [thread overview]
Message-ID: <loom.20090622T151046-988@post.gmane.org> (raw)
I was looking at file systems for Linux, Ubuntu in particular. I really like
Sun's ZPF. ZPF's copy-on-write transaction model strikes me as the correct
way to go. But ZPF lacks a GNU General Public License which blocks ZPF's
adoption by the Linux kernel. This led me to btrfs.
I understand that the B-TRee File System is a "copy-on-write file system for
Linux announced by Oracle in 2007 and published under the GNU General Public
License (GPL)".
For planning purposes, what timeframe do you see for releasing a stable
version of btrfs? I am not a paying customer nor am I an annoying manager. I
am just curious as to when I should plan to start paying closer attention. 4Q
2009? 2Q 2010?
Ext4 is a jornaling file system. A copy-on-write file system should just be
so much better. I find it hard to wait. :-)
--Thank you,
--Mike Ramsey
next reply other threads:[~2009-06-22 15:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 15:53 Mike Ramsey [this message]
[not found] ` <f058a9c30906230308m2062bbdbs519d65389400e39e@mail.gmail.com>
2009-06-23 10:09 ` Release plan Miguel F Mascarenhas Sousa Filipe
2009-06-24 1:11 ` Mike Ramsey
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.20090622T151046-988@post.gmane.org \
--to=michael.j.ramsey@lmco.com \
--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