From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <1373651458.17876.103.camel@gandalf.local.home> Subject: Re: [Ksummit-2013-discuss] When to push bug fixes to mainline From: Steven Rostedt To: Greg Kroah-Hartman Cc: "H. Peter Anvin" , stable@vger.kernel.org, linux-kernel@vger.kernel.org, ksummit-2013-discuss@lists.linux-foundation.org, torvalds@linux-foundation.org Date: Fri, 12 Jul 2013 13:50:58 -0400 In-Reply-To: <20130712172836.GA7627@kroah.com> References: <20130711214830.611455274@linuxfoundation.org> <20130712005023.GB31005@thunk.org> <20130712025745.GA24086@tuxdriver.com> <20130712033430.GA3798@kroah.com> <51E03AEE.5010403@zytor.com> <20130712172836.GA7627@kroah.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: On Fri, 2013-07-12 at 10:28 -0700, Greg Kroah-Hartman wrote: > Yes, this requires you to remember to do this after it hits Linus's > tree, so you could do like David does for networking, and keep a > seperate tree to send to me specifically for stable patches. I think he > uses patchwork, but I know others use git for this, and that's fine as > well. Perhaps just make a separate stable branch, where you cherry-pick the specific patch using the -x option. Adds a "(cherry picked from commit ...)". Then you could have some filter that monitors Linus commits and when a commit matches one of these patches, have it automatically sent to the stable list. -- Steve