mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Frey <cdfrey@foursquare.net>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Linux 3.0.24
Date: Thu, 15 Mar 2012 13:28:28 -0400	[thread overview]
Message-ID: <20120315172828.GA29721@foursquare.net> (raw)
In-Reply-To: <20120315165812.GA10397@kroah.com>

On Thu, Mar 15, 2012 at 09:58:12AM -0700, Greg KH wrote:
> On Thu, Mar 15, 2012 at 12:51:08PM -0400, 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?
> 
> This has been discussed endlessly in the past, please see the lkml
> archives for details if you are interested.  It all comes down to the
> issue, how do you classify a bug fix as a specific "kind"[1]?
> 
> Is there some reason you don't trust me in my usage of the word "must"
> here?  If so, then please feel free to go through all of the individual
> patches, which I post, and make the judgement call for yourself.
> 
> [1] Hint, for the most part, you can't.

It's not a matter of trust, but of understanding.  If, according to your
footnote, you do not classify bugs at all (except maybe compile issues,
as Jonathan mentioned), then "must" merely implies that "a bug was fixed."

But had you classified bugs, then it would be useful to know what
criteria you had used.  And if so, it would make sense that such criteria
would be documented somewhere.

I had assumed the latter case, but it seems that the former is more accurate.

Thanks, both to you and Jonathan for clarifying my misunderstanding.

- Chris


      reply	other threads:[~2012-03-15 17:28 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
2012-03-15 16:58       ` Greg KH
2012-03-15 17:28         ` Chris Frey [this message]

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=20120315172828.GA29721@foursquare.net \
    --to=cdfrey@foursquare.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jrnieder@gmail.com \
    --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®