From: Greg KH <greg@kroah.com>
To: Stefan Bader <stefan.bader@canonical.com>
Cc: linux-kernel@vger.kernel.org, stable@kernel.org,
kernel-team@lists.ubuntu.com
Subject: Re: [stable] Linux 2.6.32.27+drm33.12
Date: Fri, 10 Dec 2010 09:44:10 -0800 [thread overview]
Message-ID: <20101210174410.GA11952@kroah.com> (raw)
In-Reply-To: <1291991638-8203-1-git-send-email-stefan.bader@canonical.com>
On Fri, Dec 10, 2010 at 03:33:58PM +0100, Stefan Bader wrote:
> I am announcing the release of the 2.6.32.27+drm33.12 stable tree.
I'm sorry, but that combination is anything but "stable".
> This tree is based on 2.6.32 and generally has all of the stable updates
> applied. Except those to the DRM subsystem, which was based on 2.6.33 and
> took updates from that upstream stable as long as that existed. It will
> continue to add patches to the DRM subsystem as long as they are valid
> according to the stable update rules (Documentation/stable_kernel_rules.txt).
You didn't follow that rule for the drm tree, so please, don't call this
a "stable" tree at all.
Also note the new name for longterm kernel releases, "longterm", not
"stable".
> DRM patches for this tree should be sent to kernel-team@lists.ubuntu.com.
Why make developers do extra work for this old kernel tree? That's not
very nice.
> This release contains patches from upstream 2.6.32.27, but dropped any patches
> to the DRM subsystem.
That doesn't seem wise, but hey, good luck with it, that's a
frankenkernel if I've ever seen one...
greg k-h
prev parent reply other threads:[~2010-12-10 17:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 14:33 [stable] Linux 2.6.32.27+drm33.12 Stefan Bader
2010-12-10 14:42 ` Piotr Hosowicz
2010-12-10 14:50 ` Stefan Bader
2010-12-10 14:56 ` Piotr Hosowicz
2010-12-10 17:44 ` Greg KH [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=20101210174410.GA11952@kroah.com \
--to=greg@kroah.com \
--cc=kernel-team@lists.ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=stefan.bader@canonical.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.