From: Chris Samuel <chris@csamuel.org>
To: linux-btrfs@vger.kernel.org
Cc: Chris Mason <clm@fb.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Btrfs part two
Date: Sat, 12 Apr 2014 11:27:17 +1000 [thread overview]
Message-ID: <349322773.2UnfDfS622@quad> (raw)
In-Reply-To: <53481D52.5070608@fb.com>
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
Hi Chris,
On Fri, 11 Apr 2014 12:50:26 PM Chris Mason wrote:
> The most important changes here are from Josef, fixing a btrfs
> regression in 3.14 that can cause corruptions in the extent allocation
> tree when snapshots are in use.
Will these regression fixes go to stable too?
cheers,
Chris
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 482 bytes --]
prev parent reply other threads:[~2014-04-12 1:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 16:50 [GIT PULL] Btrfs part two Chris Mason
2014-04-12 1:27 ` 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=349322773.2UnfDfS622@quad \
--to=chris@csamuel.org \
--cc=clm@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).