From: Greg KH <gregkh@suse.de>
To: "J.H." <warthog9@kernel.org>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
Dave Young <hidave.darkstar@gmail.com>,
webmaster@kernel.org, Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
stable@kernel.org
Subject: Re: mm/-next release on kernel.org web page?
Date: Wed, 26 Aug 2009 20:33:15 -0700 [thread overview]
Message-ID: <20090827033315.GA32648@suse.de> (raw)
In-Reply-To: <4A95D677.2020807@kernel.org>
On Wed, Aug 26, 2009 at 05:42:31PM -0700, J.H. wrote:
>
> Not to reply to myself, but I've pushed out an update that should
> incorporate the expected trees now, this does eliminate the 2.2 and all
> but the last 2.4 tree (2.4.37.5), but does include all of the stable
> 2.6.x trees, the snapshots and linux-next. Frontpage, finger and rss
> should all be showing the new information universally. I'll probably
> tweak things a bit more (layout and such for the rss & html) but the
> kernels should now be listed as people expect.
This looks a lot better, thanks. But note that the 2.6.28 and 2.6.29
stable series are no longer maintained, and the current versions of them
have known security issues, so it might not be a good idea to show that
they are recommended for use at all.
Is there some way that we can "mark" activly maintained releases to have
them show up on the front page in any way? We can use the LATEST-IS
type file in the kernel directory if you want, that would be a simple
way to maintain this information.
thanks,
greg k-h
next prev parent reply other threads:[~2009-08-27 3:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 7:56 mm/-next release on kernel.org web page? Dave Young
2009-08-02 14:48 ` Stephen Rothwell
2009-08-03 1:54 ` Dave Young
2009-08-02 16:55 ` Randy Dunlap
2009-08-03 2:08 ` Dave Young
2009-08-03 2:30 ` Randy Dunlap
2009-08-03 5:01 ` J.H.
2009-08-27 0:42 ` J.H.
2009-08-27 3:33 ` Greg KH [this message]
2009-08-27 22:03 ` J.H.
2009-08-27 14:39 ` Dave Young
2009-08-27 19:43 ` Randy Dunlap
2009-08-27 20:57 ` J.H.
2009-08-27 21:46 ` Andrew Morton
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=20090827033315.GA32648@suse.de \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=hidave.darkstar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=stable@kernel.org \
--cc=warthog9@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