lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 26 Aug 2009 20:33:15 -0700
From:	Greg KH <gregkh@...e.de>
To:	"J.H." <warthog9@...nel.org>
Cc:	Randy Dunlap <rdunlap@...otime.net>,
	Dave Young <hidave.darkstar@...il.com>, webmaster@...nel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	stable@...nel.org
Subject: Re: mm/-next release on kernel.org web page?

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ