From: Chris Samuel <chris@csamuel.org>
To: Marc MERLIN <marc@merlins.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Which kernel is safe to upgrade to for btrfs?
Date: Mon, 21 May 2012 16:00:25 +1000 [thread overview]
Message-ID: <4FB9D9F9.5040907@csamuel.org> (raw)
In-Reply-To: <20120521052220.GD15765@merlins.org>
On 21/05/12 15:22, Marc MERLIN wrote:
> Have the free space problems been fixed in 3.3.x or is the 3.4.x branch
> better or should I stay with 3.2.x for safety?
There have been some fixes pushed back from the development tree into
the stable tree for 3.3.x (for the first time in btrfs's history I
believe) but there's a lot more work been happening in 3.4.
I'm happily sat on 3.2 and I would suggest sticking there too for a
while and watch what user reports come back for the 3.4 kernel (just out).
Just my 2p's worth..
cheers,
Chris
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
prev parent reply other threads:[~2012-05-21 6:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 5:22 Which kernel is safe to upgrade to for btrfs? Marc MERLIN
2012-05-21 6:00 ` Chris Samuel [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=4FB9D9F9.5040907@csamuel.org \
--to=chris@csamuel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=marc@merlins.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).