From: Matthias Andree <matthias.andree@gmx.de>
To: Nathan Scott <nathans@sgi.com>, stable@kernel.org
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.17.[1-6] XFS Filesystem Corruption, Where is 2.6.17.7?
Date: Tue, 25 Jul 2006 23:07:16 +0200 [thread overview]
Message-ID: <20060725210716.GC4807@merlin.emma.line.org> (raw)
In-Reply-To: <20060725084624.C2090627@wobbly.melbourne.sgi.com>
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
next prev parent reply other threads:[~2006-07-25 21:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-24 16:29 Justin Piszcz
2006-07-24 16:40 ` Justin Piszcz
2006-07-24 22:22 ` Daniel Drake
2006-07-24 22:46 ` Nathan Scott
2006-07-25 21:07 ` Matthias Andree [this message]
2006-07-25 21:09 ` Matthias Andree
2006-07-28 23:26 ` [stable] " Greg KH
2006-07-28 23:55 ` Dave Jones
2006-07-29 0:27 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060725210716.GC4807@merlin.emma.line.org \
--to=matthias.andree@gmx.de \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nathans@sgi.com \
--cc=stable@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®