[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20060725210716.GC4807@merlin.emma.line.org>
Date: Tue, 25 Jul 2006 23:07:16 +0200
From: Matthias Andree <matthias.andree@....de>
To: Nathan Scott <nathans@....com>, stable@...nel.org
Cc: 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, Nathan Scott wrote:
> On Mon, Jul 24, 2006 at 12:29:48PM -0400, Justin Piszcz wrote:
> > Beginning at 2.6.17 to 2.6.17.6, there is a serious XFS bug that results
> > in filesystem corruption, there was a 1 line bugfix patch that was
> > released recently and I was wondering when 2.6.17.7 would be released with
> > that patch? ...
>
> I think everyone's been real busy leading up to OLS, and many folks
> are probably taking some time off in Canada too. I know I would be
> if I was over there. ;)
I don't mean to be nasty, but the effect this has on readers, in spite
of the smiley, is that "Linux hasn't grown up yet if they find Ottawa so
much kewler than fixing a simple bug". Meaning: the downside of public
discussion is that it's easy to be mistaken.
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.
(Please remember to Cc: replies, particularly I'm not subscribed to stable)
--
Matthias "2.6.16.27 works for my Samba" 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/
Powered by blists - more mailing lists