On Wed, 2012-12-12 at 12:26 -0500, Steven Rostedt wrote: > On Wed, 2012-12-12 at 08:39 -0800, [email protected] wrote: > > The patch below does not apply to the 3.0-stable tree. > > If someone wants it applied there, or to any other stable or longterm > > tree, then please email the backport, including the original git commit > > id to <[email protected]>. > > Posted early where you complained to me about it. > > https://lkml.org/lkml/2012/11/30/315 >
So I guess the question is: what's the best way to handle stable backport process? When I fixed the bug, I realized that it was a bug for older stable releases and that the current fix wont apply cleanly to the older versions. So while the bug fix was fresh in my mind, I did the back ports to the necessary stable releases. I then posted the changes to LKML and had to wait for Ingo to pull and push to Linus (which was a while). I replied to the post and sent the backports, which all Cc'd the stable list. But that broke your process. I was hoping that sending to the stable list, that your scripts may be able to pick it up somehow when the main commit hit mainline. Is the process just to keep those backports locally on my box somewhere and wait for the FAILED reports, and then send them? I actually don't even have a copy of those backports anymore because I figured I have the email. Well, I do have the copies in my sent folder. Want me to just repost them to you? -- Steve -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
