From: Chris Frey <cdfrey@foursquare.net>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Linux 3.0.24
Date: Thu, 15 Mar 2012 12:51:08 -0400 [thread overview]
Message-ID: <20120315165108.GA27737@foursquare.net> (raw)
In-Reply-To: <20120315163749.GA25001@kroah.com>
On Thu, Mar 15, 2012 at 09:37:49AM -0700, Greg KH wrote:
> On Thu, Mar 15, 2012 at 12:23:22PM -0400, Chris Frey wrote:
> > On Mon, Mar 12, 2012 at 01:34:51PM -0700, Greg KH wrote:
> > > I'm announcing the release of the 3.0.24 kernel.
> > >
> > > All users of the 3.0 kernel series must upgrade.
> >
> > Is the word "must" defined anywhere?
>
> Surely you have a dictionary somewhere?
>
>
> > When I read it, it looks like there are serious patches included in
> > this release, perhaps data integrity or security patches. But "must"
> > has been in an awful lot of these release notes lately, that it makes
> > me wonder if it is boilerplate.
> >
> > Just curious how to interpret this.
>
> Interpret it as written please.
Perhaps it would help if I phrased my question differently: What kind of
bug makes you decide to write "must" instead of something else?
- Chris
next prev parent reply other threads:[~2012-03-15 16:51 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 [this message]
2012-03-15 16:57 ` Jonathan Nieder
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=20120315165108.GA27737@foursquare.net \
--to=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
Powered by JetHome