linux-kernel - Re: [PATCH] Documentation: Update stable address

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] [day] [month] [year] [list]

Message-Id: <201201042257.15631.arnd@arndb.de>
Date:	Wed, 4 Jan 2012 22:57:15 +0000
From:	Arnd Bergmann <arnd@...db.de>
To:	Randy Dunlap <rdunlap@...otime.net>
Cc:	Joe Perches <joe@...ches.com>,
	"Greg Kroah-Hartman" <greg@...ah.com>, stable@...r.kernel.org,
	Harry Wei <harryxiyou@...il.com>,
	xiyoulinuxkernelgroup@...glegroups.com,
	Tsugikazu Shibata <tshibata@...jp.nec.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Documentation: Update stable address

On Wednesday 04 January 2012, Randy Dunlap wrote:
> > @@ -275,8 +275,8 @@ versions.
> >  If no 2.6.x.y kernel is available, then the highest numbered 2.6.x
> >  kernel is the current stable kernel.
> >  
> > -2.6.x.y are maintained by the "stable" team <stable@...nel.org>, and are
> > -released as needs dictate.  The normal release period is approximately 
> > +2.6.x.y are maintained by the "stable" team <stable@...r.kernel.org>, and
> > +are released as needs dictate.  The normal release period is approximately
> >  two weeks, but it can be longer if there are no pressing problems.  A
> >  security-related problem, instead, can cause a release to happen almost
> >  instantly.

Shouldn't the text get reworded as well to include the 3.x.y stable releases
and rename the 2.6.x.y releases to "longterm" instead of "stable"?

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