From: Jonathan Nieder <jrnieder@gmail.com>
To: Chris Frey <cdfrey@foursquare.net>
Cc: Greg KH <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Linux 3.0.24
Date: Thu, 15 Mar 2012 11:57:36 -0500 [thread overview]
Message-ID: <20120315165736.GA11496@burratino> (raw)
In-Reply-To: <20120315165108.GA27737@foursquare.net>
Chris Frey wrote:
> Perhaps it would help if I phrased my question differently: What kind of
> bug makes you decide to write "must" instead of something else?
My impression is that Greg does not want to be in the business of
deciding which updates are security-critical. Others can make that
judgement based on the patches listed.
"All users must upgrade" would generally mean that it is prudent for
all users to upgrade, rather than some particular subset of them
(e.g., users who have been experiencing build failures).
Hope that helps,
Jonathan
next prev parent reply other threads:[~2012-03-15 16:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 20:34 Greg KH
2012-03-12 20:35 ` Greg KH
2012-03-15 10:48 ` stable-3.0: s390 build breakage [was: Linux 3.0.24] Jiri Slaby
2012-03-15 15:09 ` Greg KH
2012-03-15 16:42 ` Willy Tarreau
2012-03-15 16:49 ` Greg KH
2012-03-15 16:27 ` Jiri Slaby
2012-03-15 16:46 ` Greg KH
2012-03-15 16:47 ` Jiri Slaby
2012-03-15 16:49 ` Willy Tarreau
2012-03-15 16:51 ` Jiri Slaby
2012-03-16 12:52 ` Jiri Slaby
2012-03-16 17:22 ` Greg KH
2012-03-15 16:23 ` Linux 3.0.24 Chris Frey
2012-03-15 16:37 ` Greg KH
2012-03-15 16:51 ` Chris Frey
2012-03-15 16:57 ` Jonathan Nieder [this message]
2012-03-15 16:58 ` Greg KH
2012-03-15 17:28 ` Chris Frey
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=20120315165736.GA11496@burratino \
--to=jrnieder@gmail.com \
--cc=cdfrey@foursquare.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.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®