Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933841Ab3GPTZi (ORCPT ); Tue, 16 Jul 2013 15:25:38 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:35181 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933319Ab3GPTZg (ORCPT ); Tue, 16 Jul 2013 15:25:36 -0400 Date: Tue, 16 Jul 2013 12:11:47 -0700 From: Greg Kroah-Hartman To: Steven Rostedt Cc: Linus Torvalds , "Luck, Tony" , David Lang , "ksummit-2013-discuss@lists.linux-foundation.org" , "linux-kernel@vger.kernel.org" , "stable@vger.kernel.org" , Willy Tarreau Subject: Re: [Ksummit-2013-discuss] When to push bug fixes to mainline Message-ID: <20130716191147.GA1680@kroah.com> References: <20130711214830.611455274@linuxfoundation.org> <20130712005023.GB31005@thunk.org> <20130712051451.GC25815@1wt.eu> <20130716165933.GU22506@sirena.org.uk> <3908561D78D1C84285E8C5FCA982C28F31C845B1@ORSMSX106.amr.corp.intel.com> <1374000084.6458.36.camel@gandalf.local.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1374000084.6458.36.camel@gandalf.local.home> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1399 Lines: 29 On Tue, Jul 16, 2013 at 02:41:24PM -0400, Steven Rostedt wrote: > On Tue, 2013-07-16 at 11:29 -0700, Linus Torvalds wrote: > > > Anyway, the point I'm making is that Q&A is limited and often even > > actively misleading ("Hey, I have three tested-by's, so it must be > > fine"), and we might actually want to have a new class of > > "non-critical patch that might be worth backporting to stable, but > > only do so after it's been in a release for some time". Because while > > it might be an "obvious" fix, maybe it's not critical enough that it > > needs to be backported _now_ - maybe it could wait a month or two, and > > get wider testing. > > Should we add another stable tag? > > Have the default Cc: stable have to wait a rc or two in mainline before > it makes its way to the stable tree. Have a stable-critical for those > that are bugs that are security fixes than need to be backported ASAP. People mark stable patches that way already today with a: Cc: stable # delay for 3.12-rc4 or some such wording. I take those and don't apply them until the noted release happens, so you can do this if needed. greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/