From: Greg KH <gregkh@linuxfoundation.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Jochen Striepe <jochen@tolot.escape.de>, Willy Tarreau <w@1wt.eu>,
Josh Boyer <jwboyer@fedoraproject.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
stable <stable@vger.kernel.org>,
lwn@lwn.net, Guenter Roeck <linux@roeck-us.net>,
Hugh Dickins <hughd@google.com>,
Johannes Berg <johannes@sipsolutions.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Proposed stable release changes
Date: Wed, 21 Aug 2013 13:16:00 -0700 [thread overview]
Message-ID: <20130821201600.GA10321@kroah.com> (raw)
In-Reply-To: <20130821200702.GA10762@nazgul.tnic>
On Wed, Aug 21, 2013 at 10:07:03PM +0200, Borislav Petkov wrote:
> On Wed, Aug 21, 2013 at 01:58:16PM -0400, Steven Rostedt wrote:
> > The point I'm making, we should be more reluctant in pulling patches
> > into stable as quick as we are. A patch ideally should simmer in
> > linux-next for a bit, then go into mainline.
>
> Oh, and it is really debatable if the sheer volume of -stable patches is
> actually warranted - several people already raised the question whether
> we should be more conservative with the stable tag. But you're probably
> going to have this as one of the topics at KS...
And I pushed back on that. Which specific stable patch should _not_
have been included?
I am going to be pickier (and already have, as some maintainers have
found out), with what I accept, but so far, the number of patches I've
rejected can be counted on one hand, a very small percentage of the
overall number of stable patches.
thanks,
greg k-h
next prev parent reply other threads:[~2013-08-21 20:16 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 22:40 Proposed stable release changes Greg KH
2013-08-20 22:58 ` Willy Tarreau
2013-08-20 23:12 ` Greg KH
2013-08-20 23:57 ` Guenter Roeck
2013-08-21 5:24 ` Willy Tarreau
2013-08-20 23:04 ` Nicholas A. Bellinger
2013-08-20 23:12 ` Greg KH
2013-08-20 23:11 ` Guenter Roeck
2013-08-20 23:17 ` Greg KH
2013-08-21 0:11 ` Guenter Roeck
2013-08-21 0:42 ` Greg KH
2013-08-20 23:40 ` Josh Boyer
2013-08-20 23:57 ` Greg KH
2013-08-21 0:41 ` Josh Boyer
2013-08-21 0:49 ` Greg KH
2013-08-21 1:03 ` Josh Boyer
2013-08-21 1:11 ` Guenter Roeck
2013-08-21 18:15 ` Greg KH
2013-08-21 5:38 ` Willy Tarreau
2013-08-21 13:37 ` Steven Rostedt
2013-08-21 17:23 ` Jochen Striepe
2013-08-21 17:58 ` Steven Rostedt
2013-08-21 20:07 ` Borislav Petkov
2013-08-21 20:16 ` Greg KH [this message]
2013-08-21 21:00 ` Borislav Petkov
2013-08-21 13:42 ` Steven Rostedt
2013-08-21 14:17 ` Willy Tarreau
2013-08-21 14:54 ` Steven Rostedt
2013-08-24 18:45 ` Stefan Richter
2013-08-21 13:48 ` Borislav Petkov
2013-08-21 17:08 ` Greg KH
2013-08-21 18:20 ` Stephen Warren
2013-08-21 18:36 ` Linus Torvalds
2013-08-21 20:00 ` Borislav Petkov
2013-08-21 20:54 ` Tony Luck
2013-08-22 8:57 ` Borislav Petkov
2013-08-22 10:59 ` Geert Uytterhoeven
2013-08-22 0:05 ` Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130821201600.GA10321@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=hughd@google.com \
--cc=jochen@tolot.escape.de \
--cc=johannes@sipsolutions.net \
--cc=jwboyer@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lwn@lwn.net \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=w@1wt.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.