From: Bardur Arantsson <spam@scientician.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Another defrag question
Date: Fri, 22 Feb 2013 06:55:45 +0100 [thread overview]
Message-ID: <kg718u$6of$1@ger.gmane.org> (raw)
In-Reply-To: <20130221215602.GH27541@twin.jikos.cz>
On 02/21/2013 10:56 PM, David Sterba wrote:
> On Thu, Feb 21, 2013 at 09:58:16PM +0100, Bardur Arantsson wrote:
>> On 02/21/2013 06:47 PM, Swâmi Petaramesh wrote:
>>> Le 21/02/2013 18:25, Hugo Mills a écrit :
>>>> Correct. But btrfs isn't at that stage yet. It's getting visibly
>>>> closer, but it's not quite there. Hence the very strong recommendation
>>>> to keep up with the latest code. Hugo.
>>>
>>> The matter is that BTRFS had many early adopters just because it is -
>>> and has been for long now - in the mainline Linux kernel, so supposed
>>> stable and good choice for the future.
>>>
>>> To be honest (and not wanting to troll, promised) this is the only
>>> single reason for which I use BTRFS on 5 of my 6 machines at home - just
>>> because I thought that "Just upgrade the distro every 6 months and it
>>> will become better and better over time, no hassle, make my life easy".
>>>
>>
>> Unfortunately many distros don't make it obvious, but Btrfs is still
>> hidden behind a giant EXPERIMENTAL label in the kernel configuration.
>
> Removed in 3.9-rc1 as a part of a broad Kconfig cleanup
>
[--snip--]
>
> is it still experimental then?
Interesting, but IMO having the experimental label taken off is a
necessary, but not sufficient condition for $X to be considered stable :).
Regards,
next prev parent reply other threads:[~2013-02-22 5:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 15:46 Another defrag question Swâmi Petaramesh
2013-02-21 15:50 ` Liu Bo
2013-02-21 15:55 ` Swâmi Petaramesh
2013-02-21 15:54 ` Calvin Walton
2013-02-21 16:01 ` Swâmi Petaramesh
2013-02-21 16:09 ` Blair Zajac
2013-02-21 16:38 ` Hugo Mills
2013-02-21 17:03 ` Swâmi Petaramesh
2013-02-21 17:25 ` Hugo Mills
2013-02-21 17:47 ` Swâmi Petaramesh
2013-02-21 20:46 ` Hugo Mills
2013-02-21 20:58 ` Bardur Arantsson
2013-02-21 21:56 ` David Sterba
2013-02-22 5:55 ` Bardur Arantsson [this message]
2013-02-21 21:31 ` Johannes Hirte
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='kg718u$6of$1@ger.gmane.org' \
--to=spam@scientician.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