linux-kernel - Re: 2.6.17.[1-6] XFS Filesystem Corruption, Where is 2.6.17.7?

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: <20060725210919.GD4807@merlin.emma.line.org>
Date:	Tue, 25 Jul 2006 23:09:19 +0200
From:	Matthias Andree <matthias.andree@....de>
To:	Nathan Scott <nathans@....com>, stable@...nel.org,
	Justin Piszcz <jpiszcz@...idpixels.com>,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.17.[1-6] XFS Filesystem Corruption, Where is 2.6.17.7?

On Tue, 25 Jul 2006, Matthias Andree wrote:

> A serious suggestion is, providing that the arguments presented (people
> busy with OLS preparations and long review queue for 2.6.17.N+1):
> 
> How about doing 2.6.17.7 as an interim release fixing just what is known
> to be critical at the point of the release, and then review the rest for
> 2.6.17.8? That would nicely fit the release early, release often - users
> like that particularly for bug fixes.

OK, 2.6.17.7 is out, but still - is this suggestion worthwhile
considering for future -stable release engineering or just crap?

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