From: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Herton Ronaldo Krzesinski <herton.krzesinski@canonical.com>,
stable@vger.kernel.org, kernel-team@lists.ubuntu.com
Subject: Re: [3.5.y.z extended stable] Linux 3.5.7.1
Date: Thu, 29 Nov 2012 18:31:35 +0100 [thread overview]
Message-ID: <201211291831.35981.a.miskiewicz@gmail.com> (raw)
In-Reply-To: <1354197892-21593-1-git-send-email-herton.krzesinski@canonical.com>
On Thursday 29 of November 2012, Herton Ronaldo Krzesinski wrote:
> I am announcing the release of the 3.5.7.1 tree of stable patches.
>
> This tree picks up the latest 3.5 stable release upstream, and add patches
> on top that were later marked for stable but can't be added to 3.5, as
> it is not anymore an stable series maintained upstream.
Could this tree become real stable release for 3.5 with typical scheme
(patches, tarballs, git tree on kernel.org) ?
Thanks,
--
Arkadiusz Miśkiewicz, arekm / maven.pl
prev parent reply other threads:[~2012-11-29 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 14:04 [3.5.y.z extended stable] Linux 3.5.7.1 Herton Ronaldo Krzesinski
2012-11-29 14:04 ` Herton Ronaldo Krzesinski
2012-11-29 17:31 ` Arkadiusz Miskiewicz [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=201211291831.35981.a.miskiewicz@gmail.com \
--to=a.miskiewicz@gmail.com \
--cc=herton.krzesinski@canonical.com \
--cc=kernel-team@lists.ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.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