From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Airlie <airlied@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: stable cc's in linux -next was Re: [BUG] x86: bootmem broken on SGI UV
Date: Sun, 10 Oct 2010 10:51:21 +1100 [thread overview]
Message-ID: <20101010105121.9ebb64aa.sfr@canb.auug.org.au> (raw)
In-Reply-To: <AANLkTikCHzaovYy+g8GBE7zwBOa-=pXk=WwQ_5ts1u5m@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]
Hi Linus,
On Sat, 9 Oct 2010 16:24:59 -0700 Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
> Quite frankly, if somebody has something in "next" (and really meant
> for the _next_ merge window, not the current one) that is marked for
> stable, I think that shows uncommonly bad taste. And that, in turn,
> means that the "stable" tag is also very debatable. It clearly cannot
> be important enough to really be for stable if it's not even being
> aggressively pushed into the current -rc.
There are 22 trees that get merged into in linux-next that are "bug fixes
for the current release" trees ... that was the list I sent you after the
-rc7 announcement (most of which I think you have since merged. In
fact, there are currently only 5 commits in those 22 trees that you have
not merged.
The other thing people do is to add such bug fixes to their -next trees
before asking you to take them.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2010-10-09 23:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-09 21:34 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 [this message]
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
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=20101010105121.9ebb64aa.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=airlied@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®