linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Rich Freeman <r-btrfs@thefreemanclan.net>
Cc: Shriramana Sharma <samjnaa@gmail.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Distro vs latest kernel for BTRFS?
Date: Fri, 22 Aug 2014 15:18:44 -0400	[thread overview]
Message-ID: <53F79794.1060307@gmail.com> (raw)
In-Reply-To: <CAGfcS_=ArzTNUGCmyhcOSL-acTgfThF5XVu_-AHVaCssmsuKkQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2143 bytes --]

On 2014-08-22 14:22, Rich Freeman wrote:
> On Fri, Aug 22, 2014 at 8:04 AM, Austin S Hemmelgarn
> <ahferroin7@gmail.com> wrote:
>>>
>> I personally use Gentoo Unstable on all my systems, so I build all my
>> kernels locally anyway, and stay pretty much in-line with the current
>> stable Mainline kernel.
> 
> "Gentoo Unstable" probably means gentoo-sources, testing version,
> which follows the stable kernel branch, but the most recent stable,
> and not the long-term stable.  gentoo-sources stable version generally
> follows the most recent longterm stable kernel (so 3.14 right now).
> I'm not sure what the exact policy is, but that is my sense of it.
> 
> So, you're still running a stable kernel most likely.  If you really
> want mainline then you want git-sources.  That follows the most recent
> mainline I believe.  Of course, if you're following it that closely
> then you probably should think about just doing a git clone and
> managing it yourself, since then you can handle patches/etc more
> easily.
> 
> I think the best option for somebody running btrfs is to stick with a
> stable kernel branch, either the current stable or a very recent
> longterm.  I wouldn't go back into 3.2 land or anything like that.
> 
> But, yes, if you had stuck with 3.14 and not gone to the current
> stable then you would have missed the compress=lzo deadlock.  So, pick
> your poison.  :)
> 
> Rich
> 
By saying 'unstable' I'm referring to the stuff delimited in portage
with the ~ARCH keywords.  Personally, I wouldn't use that term myself
(all of my systems running on such packages have been rock-solid stable
from a software perspective), but that is how the official documentation
refers to things with the ~ARCH keywords.  There are a lot of Gentoo
users who don't know about the keyword thing other than as an occasional
inconvenience when emerging certain packages, so I just use the same
term as the documentation.

For the record, I am using the gentoo-sources package, but instead of
using what they mark as stable (which is 3.14), I'm using the most
recent version (which is 3.16.1).


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2455 bytes --]

  reply	other threads:[~2014-08-22 19:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-22 11:59 Distro vs latest kernel for BTRFS? Shriramana Sharma
2014-08-22 12:04 ` Austin S Hemmelgarn
2014-08-22 18:09   ` Duncan
2014-08-22 18:22   ` Rich Freeman
2014-08-22 19:18     ` Austin S Hemmelgarn [this message]
2014-08-22 14:10 ` Marc MERLIN
2014-08-22 16:51 ` Chris Murphy
2014-08-22 17:38 ` Martin Steigerwald
2014-08-25  1:06 ` Qu Wenruo

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=53F79794.1060307@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=r-btrfs@thefreemanclan.net \
    --cc=samjnaa@gmail.com \
    /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).