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: Sat, 9 Oct 2010 16:51:41 -0700 [thread overview]
Message-ID: <20101009235141.GB15564@kroah.com> (raw)
In-Reply-To: <AANLkTikCHzaovYy+g8GBE7zwBOa-=pXk=WwQ_5ts1u5m@mail.gmail.com>
On Sat, Oct 09, 2010 at 04:24:59PM -0700, Linus Torvalds wrote:
> On Sat, Oct 9, 2010 at 2:34 PM, Dave Airlie <airlied@gmail.com> wrote:
> >
> > Do we track people dong this at all? I wonder how many patches in
> > linux-next have cc: stable in them but haven't been submitted to
> > Linus,
>
> The other side of that coin is to wonder how many patches get marked
> as "stable" when they definitely shouldn't be.
>
> I know that's a non-empty set. Too many developers think that the
> thing they fix is so important that it needs to be backported. And it
> doesn't help that Greg is sometimes over-eager to take things without
> them being even in my tree long enough to get much testing.
That's a tough thing to judge as I usually batch up stable
patches/releases every other week or so. This can cause some patches to
be in your tree longer than others.
Should I just have a general "wait a week/release" type rule here before
adding them to a stable tree for most patches that aren't "obvious"?
thanks,
greg k-h
next prev parent reply other threads:[~2010-10-09 23:52 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 [this message]
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
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=20101009235141.GB15564@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