From: Dave Jones <davej@redhat.com>
To: Greg KH <greg@kroah.com>
Cc: Nathan Scott <nathans@sgi.com>,
stable@kernel.org, Justin Piszcz <jpiszcz@lucidpixels.com>,
linux-kernel@vger.kernel.org
Subject: Re: [stable] 2.6.17.[1-6] XFS Filesystem Corruption, Where is 2.6.17.7?
Date: Fri, 28 Jul 2006 19:55:34 -0400 [thread overview]
Message-ID: <20060728235534.GE3217@redhat.com> (raw)
In-Reply-To: <20060728232654.GB2140@kroah.com>
On Fri, Jul 28, 2006 at 04:26:54PM -0700, Greg Kroah-Hartman wrote:
> > OK, 2.6.17.7 is out, but still - is this suggestion worthwhile
> > considering for future -stable release engineering or just crap?
>
> .7 took a bit longer than expected, due to some security bugs that
> needed to be added to the queue, combined with the fact that both Chris
> and I were busy with OLS stuff. Normally we both aren't travelling at
> the same time, but right then, we were, so we couldn't respond as
> quickly as it seems some people felt we should have.
>
> Sorry about this, we'll try to do better next time.
The flipside to this is that those patches had been posted for around a
week before you released .7, and *no-one* caught this problem until
after the release.
The burden of testing shouldn't solely be on the -stable team.
Perhaps a -pre release at the time of review would be a good idea.
Just a roll-up of the proposed patches, to save testers having
to save and apply 30 patches seperately ?
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-07-28 23:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-24 16:29 2.6.17.[1-6] XFS Filesystem Corruption, Where is 2.6.17.7? 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
2006-07-25 21:09 ` Matthias Andree
2006-07-28 23:26 ` [stable] " Greg KH
2006-07-28 23:55 ` Dave Jones [this message]
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=20060728235534.GE3217@redhat.com \
--to=davej@redhat.com \
--cc=greg@kroah.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.