From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Backporting bugfixes
Date: Wed, 18 Dec 2013 21:01:09 +0000 (UTC) [thread overview]
Message-ID: <pan$d376f$c26d0392$a268b32d$b503d0c7@cox.net> (raw)
In-Reply-To: 20131218143153.4ffeb40a@IRBT4585
Pavel Roskin posted on Wed, 18 Dec 2013 14:31:53 -0500 as excerpted:
> On Wed, 18 Dec 2013 19:23:08 +0000 Chris Mason <clm@fb.com> wrote:
>
>> 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.
>
> That's great news! Thank you for a quick reply!
In fact, here's the stable-queue request.
<http://permalink.gmane.org/gmane.linux.kernel.stable/73711
(It was cross-posted to both the btrfs and stable lists. =:^)
That said, while btrfs bugfixes are generally being submitted to stable
when appropriate, as with all stable-tree patches since they aren't
eligible for stable until they've hit the development kernel, the fastest
(non-btrfs-next or direct-off-the-list) way to get them is to run either
that development kernel.
Which isn't entirely inappropriate in any case, given that while the
btrfs kconfig warnings were turned down some in 3.12, it's still under
heavy development such that users who choose to run it are choosing to
run a not yet fully stable filesystem, and if they're already risking
their data on that, they might as well run a full development kernel too.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
prev parent reply other threads:[~2013-12-18 21:01 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
2013-12-18 19:31 ` Pavel Roskin
2013-12-18 21:01 ` Duncan [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='pan$d376f$c26d0392$a268b32d$b503d0c7@cox.net' \
--to=1i5t5.duncan@cox.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;
as well as URLs for NNTP newsgroup(s).