linux-kernel - Re: -longterm kernels

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]

Message-ID: <1304831361.6326.21.camel@marge.simson.net>
Date:	Sun, 08 May 2011 07:09:21 +0200
From:	Mike Galbraith <efault@....de>
To:	Stanislaw Gruszka <sgruszka@...hat.com>
Cc:	Greg KH <greg@...ah.com>, stable@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: -longterm kernels

On Sat, 2011-05-07 at 16:55 +0200, Stanislaw Gruszka wrote:
> On Thu, May 05, 2011 at 08:25:01AM -0700, Greg KH wrote:
> > > BTW, Greg, perhaps -logterm releasing policy should be revised somehow.
> > > Currently we have .32, .33, .34, .35 -longterm, what is kind a much.
> > 
> > It's not "much" if you rely on that kernel version, right?
> 
> Yes, but maybe would be better if they do not relay on some versions in
> long term manner, and i.e. .33 users would use .32 and .34 users would
> use .35 instead?

Ceasing to rely upon .33 isn't a trivial choice for -rt tree users.

	-Mike

--
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/