linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: Sjoerd <sjoerd@sjomar.eu>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Latest kernel to use?
Date: Thu, 24 Sep 2015 21:18:50 +0000	[thread overview]
Message-ID: <20150924211850.GD3749@carfax.org.uk> (raw)
In-Reply-To: <4362384.AA8xu4anSN@hoefnix>

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

On Thu, Sep 24, 2015 at 11:07:32PM +0200, Sjoerd wrote:
> Maybe a silly question for most of you, but the wiki states to always try to 
> use the latest kernel with btrfs. Which one would be best: 
> - 4.2.1 (currently latest stable and matches the btrfs-progs versioning) or
> - the 4.3.x (mainline)?
> 
> Stable sounds more stable to me(hence the name ;) ), but the mainline kernel 
> seems to be in more active development?

   I'd suggest sticking to the 4.2 series for now. 4.3 will be in
pre-release state for another couple of months (give or take).

   Hugo.

-- 
Hugo Mills             | In event of Last Trump, please form an orderly queue
hugo@... carfax.org.uk | and await judgement.
http://carfax.org.uk/  |
PGP: E2AB1DE4          |     Unofficial notice in Cambridge University Library

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2015-09-24 21:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24 21:07 Latest kernel to use? Sjoerd
2015-09-24 21:18 ` Hugo Mills [this message]
2015-09-25 11:20 ` Austin S Hemmelgarn
2015-09-25 13:12   ` Rich Freeman
2015-09-25 13:43     ` Roman Mamedov
     [not found]     ` <CAEp_DRB7zaHmJnghJzVR++_OO+4mrM_+jCjrYAQJcNUXpM=bAQ@mail.gmail.com>
2015-09-25 17:00       ` Rich Freeman
2015-09-25 17:41         ` Bostjan Skufca
2015-09-25 13:36 ` Sjoerd
2015-09-25 13:51   ` Hugo Mills
2015-09-25 14:34     ` Bostjan Skufca
2015-09-26  2:04       ` Duncan
2015-09-25 14:35     ` Sjoerd

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=20150924211850.GD3749@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sjoerd@sjomar.eu \
    /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).