linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Shriramana Sharma <samjnaa@gmail.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Distro vs latest kernel for BTRFS?
Date: Mon, 25 Aug 2014 09:06:03 +0800	[thread overview]
Message-ID: <53FA8BFB.1000604@cn.fujitsu.com> (raw)
In-Reply-To: <CAH-HCWVMO+NO0B5i0o0gCHBy9dLjc08gcqxT7oEV5WkO2BHvMA@mail.gmail.com>

Personally, if doing development, compiling from latest stable or 
integration kernel is my choice.

But if not developing the codes, I prefer Arch's core repo, which is 
about 1~2 weeks late than the stable release.
Although somewhat late, but still much newer than most distros' stable repo.
(I also used to use Gentoo, but even with ccache, compiling everything 
is somewhat time killing and overkilled for me)

Thanks,
Qu
-------- Original Message --------
Subject: Distro vs latest kernel for BTRFS?
From: Shriramana Sharma <samjnaa@gmail.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Date: 2014年08月22日 19:59
> Hello. I've seen repeated advices to use the latest kernel. While
> hearing of the recent compression bug affecting recent kernels does
> somewhat warn one off the previous advice, I would like to know what
> people who are running regular distros do to get the latest kernel.
>
> Personally I'm on Kubuntu, which provides mainline kernels till a
> particular point but not beyond that.
>
> Do people here always compile the latest kernel themselves just to get
> the latest BTRFS stability fixes (and  improvements, though as a
> second priority)?
>


      parent reply	other threads:[~2014-08-25  1:06 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
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 [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=53FA8BFB.1000604@cn.fujitsu.com \
    --to=quwenruo@cn.fujitsu.com \
    --cc=linux-btrfs@vger.kernel.org \
    --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).