From: Chris Mason <clm@fb.com>
To: "proski@gnu.org" <proski@gnu.org>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Backporting bugfixes
Date: Wed, 18 Dec 2013 19:23:08 +0000 [thread overview]
Message-ID: <1387394605.25093.4.camel@ret.masoncoding.com> (raw)
In-Reply-To: <20131218140615.dbjsgs7zkssgckos-cebfxv@webmail.spamcop.net>
On Wed, 2013-12-18 at 14:06 -0500, Pavel Roskin wrote:
> Hello!
>
> I have noticed that there have been important fixes for btrfs in the
> mainline Linux git repository. However, there is just one btrfs fix
> in Linux 3.12.5 after 3.12.
>
> I think it's important to submit all serious bugfixes to the stable
> kernels. It would protect users against data corruption and improve
> the image of btrfs as a serious filesystem that can be trusted at
> least with semi-important data.
>
> This post was inspired by http://lwn.net/Articles/577218/ and
> https://bugzilla.redhat.com/show_bug.cgi?id=1028750
>
Hi Pavel,
We do tag some commits for stable, but Dave Sterba actually just sent a
request to the stable tree to pull in a few more.
-chris
next prev parent reply other threads:[~2013-12-18 19:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 19:06 Backporting bugfixes Pavel Roskin
2013-12-18 19:23 ` Chris Mason [this message]
2013-12-18 19:31 ` Pavel Roskin
2013-12-18 21:01 ` Duncan
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=1387394605.25093.4.camel@ret.masoncoding.com \
--to=clm@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=proski@gnu.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).