From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 1944A1381F3 for ; Wed, 24 Jul 2013 19:15:27 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CE27AE09F3; Wed, 24 Jul 2013 19:15:18 +0000 (UTC) Received: from foo.stuge.se (foo.stuge.se [212.116.89.98]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 83A03E09C0 for ; Wed, 24 Jul 2013 19:15:17 +0000 (UTC) Received: (qmail 16759 invoked by uid 501); 24 Jul 2013 19:15:15 -0000 Message-ID: <20130724191515.16758.qmail@stuge.se> Date: Wed, 24 Jul 2013 21:15:15 +0200 From: Peter Stuge To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Vanilla sources stabilization policy change Mail-Followup-To: gentoo-dev@lists.gentoo.org References: <1462872.zkzQFHQRNq@comanche> <20130724173751.8848.qmail@stuge.se> <51F0125D.2090500@yahoo.ca> <20130724175410.10332.qmail@stuge.se> <20130724190130.15592.qmail@stuge.se> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Archives-Salt: b8459005-eafe-4303-aeef-50eb56d8ab23 X-Archives-Hash: 973b89d9f96265c31051a6e04ab04906 Ben Kohler wrote: > > I am suggesting that the latest available upstream kernel should > > perhaps be the default for Gentoo users. > > You seem to be ignoring the regressions that often come with new kernel > releases, the very common breakage caused in stable "genkernel all", and > other various complications. Unleashing brand new kernel.org sources on > stable users as soon as they are released seems crazy to me. I don't know, I think it makes a lot of sense.. Users who upgrade their kernels (don't upgrade if you don't want to) would be able to participate upstream with reports and confirmations. > These releases surely bring more than just "the newest fixes". It varies but sure, I think users should inform themselves about the new version (of any package!) before they actually upgrade it. //Peter