From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 817D113832E for ; Sun, 21 Aug 2016 14:23:55 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 88D02E0B4D; Sun, 21 Aug 2016 14:23:45 +0000 (UTC) Received: from smarthost01d.mail.zen.net.uk (smarthost01d.mail.zen.net.uk [212.23.1.7]) by pigeon.gentoo.org (Postfix) with ESMTP id 687B5E08C6 for ; Sun, 21 Aug 2016 14:23:44 +0000 (UTC) Received: from [82.69.80.10] (helo=peak.localnet) by smarthost01d.mail.zen.net.uk with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1bbTf4-000BYx-UN for gentoo-user@lists.gentoo.org; Sun, 21 Aug 2016 14:23:43 +0000 From: Peter Humphrey To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] What's happened to gentoo-sources? Date: Sun, 21 Aug 2016 15:23:42 +0100 Message-ID: <4803995.pTVfW4lmFR@peak> User-Agent: KMail/4.14.10 (Linux/4.7.2-gentoo; KDE/4.14.23; x86_64; ; ) In-Reply-To: References: <3719941.fjHdSEpZyq@peak> <3696924.CMMy0m93A0@peak> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Originating-smarthost01d-IP: [82.69.80.10] X-Archives-Salt: e64ad72c-389b-4eeb-8a76-d6d15f7452cf X-Archives-Hash: c6dcae63dd188f394a0a7d8dc00ff3df 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. > (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? --->8 > 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. > I tend to stay on the next-to-most-recent longterm not long after a new > longterm is announced. That tends to give them enough time to work > out the bugs. Plus, I spend a lot less time playing with > configuration options this way (they don't change within a minor > version). Sound policy, I'm sure. How does an ordinary mortal know which versions are here for the long term? -- Rgds Peter