From: Willy Tarreau <w@1wt.eu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Josh Boyer <jwboyer@fedoraproject.org>,
Greg KH <gregkh@linuxfoundation.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>,
Borislav Petkov <bp@alien8.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Proposed stable release changes
Date: Wed, 21 Aug 2013 16:17:25 +0200 [thread overview]
Message-ID: <20130821141725.GB20685@1wt.eu> (raw)
In-Reply-To: <20130821134248.GB16493@home.goodmis.org>
On Wed, Aug 21, 2013 at 09:42:48AM -0400, Steven Rostedt wrote:
> Personally, I still let my stable patches that go into later -rc sit
> in linux-next for a few days before pushing them to mainline. I may even
> wait for the next -rc to push it just to make sure the patch wont cause
> more issues. But I know others that just send the fix directly to
> mainline without going through linux-next. Those, I would think, are the
> most prone to cause issues in stable.
This is also what I suspected though I have no data to confirm or deny that.
If this happens to be the case, maybe then there should be some barrier such
as :
- everything merged at -rc4 or before gets backported after the next -rc
- everything from -rc5 and upper waits for next -rc1 unless tagged urgent ?
Willy
next prev parent reply other threads:[~2013-08-21 14:20 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 22:40 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
2013-08-21 21:00 ` Borislav Petkov
2013-08-21 13:42 ` Steven Rostedt
2013-08-21 14:17 ` Willy Tarreau [this message]
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=20130821141725.GB20685@1wt.eu \
--to=w@1wt.eu \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=hughd@google.com \
--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 \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®