From: Greg KH <gregkh@suse.de>
To: "Ozan Çağlayan" <ozan@pardus.org.tr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.28.10
Date: Sat, 2 May 2009 14:50:11 -0700 [thread overview]
Message-ID: <20090502215011.GA17424@suse.de> (raw)
In-Reply-To: <49FCBF1C.1060603@pardus.org.tr>
On Sun, May 03, 2009 at 12:46:04AM +0300, Ozan Çağlayan wrote:
> Greg KH wrote:
> > I'm announcing the release of the 2.6.28.10 kernel.
> >
> > It contains a wide range of bugfixes, and all users of the 2.6.28 kernel
> > series are strongly encouraged to upgrade. Especially due to the CVE
> > issues that are fixed here.
> >
> > NOTE, this is the LAST update of the 2.6.28 kernel series, so all users
> > are very strongly encouraged to upgrade to the 2.6.29 series at this
> > point in time!
> >
> Hi,
>
> Is there a policy about the end-of-life of kernel releases? 2.6.27 is at
> .21 while
> .10 is the last update for 2.6.28.
"Policy"? heh, no :)
It has been repeated many times that the 2.6.27 tree is going to be
maintained for a long time. That is why I am still doing .27 releases,
and will be for quite a while.
The other -stable branches are moving just like they always have been,
nothing is new there.
Hope this helps,
greg k-h
next prev parent reply other threads:[~2009-05-02 21:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-02 20:04 Linux 2.6.28.10 Greg KH
2009-05-02 20:04 ` Greg KH
2009-05-02 21:46 ` Ozan Çağlayan
2009-05-02 21:50 ` Greg KH [this message]
2009-05-02 22:10 ` Ozan Çağlayan
2009-05-04 15:30 ` Linux 2.6.28.10 (ocfs2 build failure) Randy Dunlap
2009-05-04 15:35 ` 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=20090502215011.GA17424@suse.de \
--to=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ozan@pardus.org.tr \
/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