[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1374003789.6458.55.camel@gandalf.local.home>
Date: Tue, 16 Jul 2013 15:43:09 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
"Luck, Tony" <tony.luck@...el.com>, David Lang <david@...g.hm>,
"ksummit-2013-discuss@...ts.linux-foundation.org"
<ksummit-2013-discuss@...ts.linux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"stable@...r.kernel.org" <stable@...r.kernel.org>,
Willy Tarreau <w@....eu>
Subject: Re: [Ksummit-2013-discuss] When to push bug fixes to mainline
On Tue, 2013-07-16 at 12:11 -0700, Greg Kroah-Hartman wrote:
> People mark stable patches that way already today with a:
> Cc: stable <stable@...r.kernel.org> # 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.
I guess the thing is, are stable patches prone to regressions. Do we
just do that for patches that we think are too complex and may cause
some harm. Of course, there's the question about having a clue about
what patches might cause harm or not.
For tracing patches, I test them probably more than most people, as
tracing isn't usually done on non development machines. A regression in
tracing isn't likely to harm others.
Right now it doesn't seem to be an issue because we have "Greg" doing
things at light speed. But when stable is maintained by a lesser deity,
then we may need to look at changing the process.
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists