Return-Path: Date: Thu, 15 Mar 2012 12:51:08 -0400 From: Chris Frey To: Greg KH Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: Linux 3.0.24 Message-ID: <20120315165108.GA27737@foursquare.net> References: <20120312203451.GA16773@kroah.com> <20120315162322.GA26005@foursquare.net> <20120315163749.GA25001@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120315163749.GA25001@kroah.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: 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