public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Airlie <airlied@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: stable cc's in linux -next was Re: [BUG] x86: bootmem broken on SGI UV
Date: Mon, 11 Oct 2010 11:32:36 -0700	[thread overview]
Message-ID: <20101011183236.GA8704@kroah.com> (raw)
In-Reply-To: <AANLkTikKNHp85iHNunSnC6EJkS5P3M5-OEN3yzzFw_Q8@mail.gmail.com>

On Mon, Oct 11, 2010 at 11:21:20AM -0700, Linus Torvalds wrote:
> On Mon, Oct 11, 2010 at 10:31 AM, Greg KH <greg@kroah.com> wrote:
> > Not that I'm trying to say, "it could be worse", just that, "what could
> > be done better?"
> 
> I really don't know. I suspect that a certain amount of problems are
> always going to be inevitable. It's not like you can avoid regressions
> entirely, at least not unless you take the "it's dead, Jim" approach
> to stable.

Yeah, I do feel I keep some of the stable trees around longer then I
should, I've been working to keep that from happening any more in the
future.

thanks,

greg k-h

  reply	other threads:[~2010-10-11 18:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-09 21:34 stable cc's in linux -next was Re: [BUG] x86: bootmem broken on SGI UV Dave Airlie
2010-10-09 23:24 ` Linus Torvalds
2010-10-09 23:38   ` Rafael J. Wysocki
2010-10-09 23:52     ` Greg KH
2010-10-09 23:59       ` Rafael J. Wysocki
2010-10-09 23:51   ` Stephen Rothwell
2010-10-09 23:51   ` Greg KH
2010-10-11 17:18     ` Linus Torvalds
2010-10-11 17:31       ` Greg KH
2010-10-11 18:21         ` Linus Torvalds
2010-10-11 18:32           ` Greg KH [this message]
2010-10-09 23:38 ` Stephen Rothwell
2010-10-09 23:50   ` Greg KH

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=20101011183236.GA8704@kroah.com \
    --to=greg@kroah.com \
    --cc=airlied@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --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