From: David Sterba <dsterba@suse.cz>
To: Pavel Volkov <sailor@lists.xtsubasa.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Linux documentation: btrfs.txt
Date: Thu, 29 Jan 2015 13:44:37 +0100 [thread overview]
Message-ID: <20150129124437.GK3641@twin.jikos.cz> (raw)
In-Reply-To: <d39d1736-4e2a-49cd-b6ef-5fdcab90bcaa@lists.xtsubasa.org>
On Wed, Jan 28, 2015 at 08:04:39PM +0300, Pavel Volkov wrote:
> In my 3.18.3 sources the file at Documentation/filesystems/btrfs.txt says:
>
> "Btrfs is under heavy development, and is not suitable for
> any uses other than benchmarking and review. The Btrfs disk format is
> not yet finalized."
>
> btrfs is no longer marked experimental in kernel and the file format is
> stable. It is suited for general use except some features.
> Maybe it's time to update btrfs.txt?
Yeah, the text hasn't been changed since 2009 and we've missed it during
the dangerous & experimental label removal. Thanks.
prev parent reply other threads:[~2015-01-29 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 17:04 Linux documentation: btrfs.txt Pavel Volkov
2015-01-29 12:44 ` David Sterba [this message]
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=20150129124437.GK3641@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=sailor@lists.xtsubasa.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).