From: Greg KH <greg@kroah.com>
To: 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 16:26:54 -0700 [thread overview]
Message-ID: <20060728232654.GB2140@kroah.com> (raw)
In-Reply-To: <20060725210919.GD4807@merlin.emma.line.org>
On Tue, Jul 25, 2006 at 11:09:19PM +0200, Matthias Andree wrote:
> 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?
.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.
greg k-h
next prev parent reply other threads:[~2006-07-28 23:50 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 ` Greg KH [this message]
2006-07-28 23:55 ` [stable] " 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=20060728232654.GB2140@kroah.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox