From: "J.H." <warthog9@kernel.org>
To: "Éric Piel" <eric.piel@tremplin-utc.net>
Cc: Greg KH <gregkh@suse.de>,
webmaster@kernel.org, LKML <linux-kernel@vger.kernel.org>,
stable@kernel.org
Subject: Re: Linux 2.6.27.28
Date: Fri, 24 Jul 2009 18:50:03 -0700 [thread overview]
Message-ID: <4A6A64CB.7090108@kernel.org> (raw)
In-Reply-To: <4A6A48A1.80608@tremplin-utc.net>
Éric Piel wrote:
> Op 25-07-09 00:27, Greg KH schreef:
>> I'm announcing the release of the 2.6.27.28 kernel. It fixes a
>> boot-time error with the 2.6.27.27 release. If you don't have this
>> problem, no need to upgrade.
>>
>> I'll also be replying to this message with a copy of the patch between
>> 2.6.27.27 and 2.6.27.28
>>
>> The updated 2.6.27.y git tree can be found at:
>> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.27.y.git
>> and can be browsed at the normal kernel.org git web browser:
>> http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.27.y.git;a=summary
>>
> Hello,
> Currently, there is no clue on www.kernel.org that 2.6.27 is a "long
> term stable" kernel tree. Would it be possible to add a line to the page
> pointing to the latest version of this type of tree? I'm sure some
> people would love discovering that such thing exists :-)
Eric, Everyone,
Yes we know about this problem, the code that generates the numbers on
the front page is really quite ancient (and thus any assumption we had
back when it was written is anything but the same now) and we have been
working on getting it updated. However there has been a lot going on,
Fedora's recent excitement, Linux Symposium, OSCon, etc and work on this
has been disrupted and scattered - I.E. I haven't gotten very far on it
yet :-(
I'm hoping to get back onto it next week, but please bear with us while
we try and get it all sorted out and try and get the code into such a
shape that we can actually cope with the ever changing idea of what are
'latest' kernels are now, and going forward.
- John 'Warthog9' Hawley
next prev parent reply other threads:[~2009-07-25 2:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 22:27 Linux 2.6.27.28 Greg KH
2009-07-24 22:28 ` Greg KH
2009-07-24 23:49 ` Éric Piel
2009-07-25 1:50 ` J.H. [this message]
2009-07-25 3:30 ` Greg KH
2009-07-25 4:18 ` Bron Gondwana
[not found] ` <ck4l6511epc17ngfdu7qu8ln46b7op9lj9@4ax.com>
2009-07-25 5:26 ` Greg KH
2009-07-25 10:34 ` Grant Coady
2009-07-25 7:25 ` Thomas Voegtle
2009-07-25 10:00 ` Thomas Meyer
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=4A6A64CB.7090108@kernel.org \
--to=warthog9@kernel.org \
--cc=eric.piel@tremplin-utc.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=webmaster@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