From: Daniel Farina <drfarina@acm.org>
To: linux-btrfs@vger.kernel.org
Subject: A little confused about what remains to make a stable release
Date: Wed, 17 Nov 2010 14:27:39 -0800 [thread overview]
Message-ID: <AANLkTi=q4bKVGfD-QoF68NecL4e4d5dfcvMrgv5NHtb3@mail.gmail.com> (raw)
Hello List,
I have been tracking the development of btrfs for some time, as the
built-in support for snapshotting would be of great convenience for
relational database use cases. I have been crawling the wiki
(especially the FAQ), but I still don't have a clear sense of "what's
left" *besides* the need for a 'fsck' utility that can be called
absolutely vital.
That, and testing and bug reports.
>From the materials I've been able to find, it's hard for me to get a
sense of how one could assist the project towards being recommended
for general use; do the denizens of this list has a sense of what
those things might be? (Or a link?)
--
fdr
next reply other threads:[~2010-11-17 22:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 22:27 Daniel Farina [this message]
2010-11-17 22:59 ` A little confused about what remains to make a stable release Hugo Mills
2010-11-18 0:46 ` Anthony Roberts
2010-11-18 6:24 ` Daniel Farina
2010-11-18 9:39 ` Hugo Mills
2010-11-18 18:22 ` Anthony Roberts
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='AANLkTi=q4bKVGfD-QoF68NecL4e4d5dfcvMrgv5NHtb3@mail.gmail.com' \
--to=drfarina@acm.org \
--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;
as well as URLs for NNTP newsgroup(s).