public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] What's happened to gentoo-sources?
Date: Sun, 21 Aug 2016 16:06:02 +0100	[thread overview]
Message-ID: <18634581.B9AcuhlFvT@peak> (raw)
In-Reply-To: <CAGfcS_mAdXSBJJan83zzEtY_uz-Wn2D2WUMSf=iKpqTHqrpy7w@mail.gmail.com>

On Sunday 21 Aug 2016 10:50:55 Rich Freeman wrote:
> On Sun, Aug 21, 2016 at 10:23 AM, Peter Humphrey <peter@prh.myzen.co.uk> 
wrote:
> > On Sunday 21 Aug 2016 07:28:17 Rich Freeman wrote:
> >> ... there is nothing wrong with having some internal QA on kernel
> >> releases.  4.1 had a nasty memory leak a release or two ago that was
> >> killing my system after only an hour or two uptime.  They took over a
> >> week to stabilize the fix as well (though a patch was out fairly
> >> quickly). So, I'm not in nearly the rush to update kernels as I used
> >> to be> 
> > I've formed the impression that a good many kernel updates are mainly
> > just to incorporate code for new devices, so I don't rush into it
> > normally either. However, this box does have some hardware that's not
> > yet a year old, so I do keep this one up to date.
> 
> The 3rd decimal almost never has code for new devices.  It is intended
> to be 100% bugfixes.  So, you generally don't want to be too far
> behind on that.
> 
> >> (granted, unless you read all the lists it is easy to miss this sort of
> >> thing).
> > 
> > Do you recommend any in particular for this? Gentoo-dev, perhaps?
> 
> Nope.  That memory leak was on lkml I think.  Only reason I spotted it
> was that I searched for it after getting bitten by it.  I doubt I'd
> have even noticed the thread but for looking for it.  I do tend to
> search the btrfs lists before switching between series, because that
> is the thing I figure is most likely to break.
> 
> Honestly, kernel QA could be better in some ways.  When some crippling
> bug comes along they don't always rush to release fixes, and they
> don't have any way to communicate with end-users.  They just assume
> that distros are paying attention to that sort of thing.  And most
> probably are (probably including Gentoo, but I'm not running a Gentoo
> kernel since the Gentoo kernels aren't really going to be optimized
> for btrfs stability).
> 
> >> I ended up bailing on gentoo-sources all the same.  Not that there was
> >> really anything wrong with it, but since I'm running btrfs and they've
> >> had a history of nasty regressions that tend to show up MONTHS later
> >> I've been a lot more picky about my kernel updates.  I'm currently
> >> tracking 4.1.  I might think about moving to 4.4 in a little while.
> > 
> > Well, according to eix, there's only 4.4.19 between 4.1.30 and 4.7.2.
> 
> Those are just the versions packaged for Gentoo.
> kernel.org has 4.4.19 as the only non-EOL version in-between, and it
> is longterm (I think 4.7 is too, but it isn't marked as such yet).
> 
> > Sound policy, I'm sure. How does an ordinary mortal know which versions
> > are here for the long term?
> 
> kernel.org
> 
> The Gentoo team will not let down ordinary users.  If you're using
> semi-experimental features then you're best off keeping a close eye on
> upstream no matter what distro you use.

OK. Thanks for your advice, Rich, as always. Also to Alarig.

-- 
Rgds
Peter



  reply	other threads:[~2016-08-21 15:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-21  9:12 [gentoo-user] What's happened to gentoo-sources? Peter Humphrey
2016-08-21  9:55 ` Rich Freeman
2016-08-21 10:20   ` Peter Humphrey
2016-08-21 11:28     ` Rich Freeman
2016-08-21 14:23       ` Peter Humphrey
2016-08-21 14:34         ` Alarig Le Lay
2016-08-21 14:50         ` Rich Freeman
2016-08-21 15:06           ` Peter Humphrey [this message]
2016-08-23  9:00           ` Tom H
2016-08-30  6:34       ` [gentoo-user] " Kai Krakow
2016-08-30  7:47         ` Neil Bothwick
2016-09-01 20:08           ` Kai Krakow
2016-09-01 20:57             ` Alan McKinnon
2016-09-01 21:56             ` Neil Bothwick
2016-09-02  0:33               ` Kai Krakow
2016-09-02  9:11                 ` Neil Bothwick
2016-09-02  2:38               ` »Q«
2016-09-01 20:14   ` Kai Krakow
2016-08-21 10:38 ` [gentoo-user] " Alarig Le Lay
2016-08-22 11:19 ` Alan Mackenzie
2016-08-22 13:23   ` Peter Humphrey
2016-08-22 13:52     ` Alan Mackenzie
2016-08-23  7:25 ` J. Roeleveld
2016-08-23  8:30   ` Peter Humphrey
2016-08-23  8:53     ` J. Roeleveld

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=18634581.B9AcuhlFvT@peak \
    --to=peter@prh.myzen.co.uk \
    --cc=gentoo-user@lists.gentoo.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