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 10:31:41 -0700 [thread overview]
Message-ID: <20101011173141.GB7116@kroah.com> (raw)
In-Reply-To: <AANLkTikBGsO9wy3z-z6_pTKq0vrYme0fEhE8KcXj_Si3@mail.gmail.com>
On Mon, Oct 11, 2010 at 10:18:34AM -0700, Linus Torvalds wrote:
> And I suspect that from a social standpoint, if we delay the stable
> queue auto-patch-sending, it will just lead to people trying to bypass
> that delay by sending things directly to stable rather than depending
> on the "stable@kernel.org" tag on the commit itself. Or if the delay
> is implemented on the stable email address itself, then people would
> try to just send it directly to you instead.
I agree, that would just get messier.
> It doesn't help that the number of patches in a stable release is much
> bigger than at least I personally envisioned. Yes, many of them are
> things like adding device ID's etc, but I do suspect that it just then
> makes it much harder to try to delay things by a week or something.
> Plus some problems probably wouldn't even be noticed in a week in the
> development kernel, and they'd _still_ be found only once it hits
> stable just because lots of people will obviously never test the
> development kernel.
The "largeness" of recent stable kernel releases (i.e. for the past
year) seem more to be a factor of the subsystem maintainers finally
realizing that they should be sending their bugfixes to me (thanks a
large part to Andrew's constant badgering about this), combined with the
distros sending me their bugfixes that they have found that are already
included upstream.
> So I have no solution to it. I just don't think stable has been quite
> as stable as people would wish for.
It hasn't? I haven't heard people saying anything about this before, in
fact, people seem to get upset at me when I reject the stuff they are
sending me for inclusion which don't meet the stable criteria.
Not that I'm trying to say, "it could be worse", just that, "what could
be done better?"
thanks,
greg k-h
next prev parent reply other threads:[~2010-10-11 17:40 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 [this message]
2010-10-11 18:21 ` Linus Torvalds
2010-10-11 18:32 ` Greg KH
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=20101011173141.GB7116@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