All of lore.kernel.org
 help / color / mirror / Atom feed
From: Piotr Hosowicz <piotr@hosowicz.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 15:56:49 +0100	[thread overview]
Message-ID: <4D023FB1.7080503@example.com> (raw)
In-Reply-To: <4D023E22.6090509@canonical.com>

On 10.12.2010 15:50, Stefan Bader wrote:
> On 12/10/2010 03:42 PM, Piotr Hosowicz wrote:
>> On 10.12.2010 15:33, Stefan Bader wrote:
>>> I am announcing the release of the 2.6.32.27+drm33.12 stable tree.
>>
>> Would you please highlight main assets of this kernel? I could try
>> something new.
>>
>> Regards,
>>
>> Piotr Hosowicz
>>
>
> As described in the body of the announcement this tree is a 2.6.32 stable tree
> with all the drm code backported from 2.6.33 (plus stable patches for that).
> It is basically what the Debian and Ubuntu 2,.6.32 kernels are based on (as the
> 2.6.32 drm code was seen as too bad).
>
> I am maintaining that tree on kernel.org, so Debian and us (or whoever had need
> for that Frankenkernel solution) to have a shared place to maintain this hybrid
> stable.

Ok, cloning happily. ;-)

-- 
"[Oleksy] dotknął naszych domów, naszych żon, naszych dzieci,
naszych psów, naszych ŚWINEK MORSKICH, on po prostu wkroczył
swoim głupim gadaniem w sferę prywatną, która musi być chro-
niona dla dobra każdego z nas" - powiedział Kwaśniewski.
NP: Peter Green Splinter Group - Burglar
NB: 2.6.37-rc5-git3

  reply	other threads:[~2010-12-10 14:56 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 [this message]
2010-12-10 17:44 ` 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=4D023FB1.7080503@example.com \
    --to=piotr@hosowicz.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.