From: Ben Hutchings <ben@decadent.org.uk>
To: David Airlie <airlied@linux.ie>
Cc: kernel-team@lists.ubuntu.com, kernel-packagers@vger.kernel.org,
dri-devel@lists.freedesktop.org, debian-kernel@lists.debian.org
Subject: DRM stable updates beyond 2.6.33.6
Date: Sun, 08 Aug 2010 06:25:10 +0100 [thread overview]
Message-ID: <1281245110.7543.308.camel@localhost> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 502 bytes --]
David,
As you know, Debian and Ubuntu (and others?) opted to use 2.6.32 as the
basis for a stable release but to take DRM from 2.6.33. Now that the
stable 2.6.33 series is over, we need some other means to communicate
the most important bug fixes for DRM that should go into these
distributions. Do you have any suggestions for how we should to this?
Could you maintain a drm-2.6.33 branch?
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next reply other threads:[~2010-08-08 5:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-08 5:25 Ben Hutchings [this message]
2010-08-08 5:39 ` DRM stable updates beyond 2.6.33.6 Ben Hutchings
2010-08-09 7:40 ` Stefan Bader
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=1281245110.7543.308.camel@localhost \
--to=ben@decadent.org.uk \
--cc=airlied@linux.ie \
--cc=debian-kernel@lists.debian.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-packagers@vger.kernel.org \
--cc=kernel-team@lists.ubuntu.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.