From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jeff Garzik <jeff@garzik.org>,
Chuck Lever <chuck.lever@oracle.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
NeilBrown <neilb@suse.de>, Adrian Bunk <bunk@stusta.de>
Subject: Re: [bisect] NFS regression breaks X
Date: Wed, 09 May 2007 20:10:13 -0400 [thread overview]
Message-ID: <1178755813.6760.26.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <20070509155228.d1b9d644.akpm@linux-foundation.org>
On Wed, 2007-05-09 at 15:52 -0700, Andrew Morton wrote:
> It's a bit rough that Jeff spent a large amount of time hunting down an
> already-known bug. That's normally my job :(
The bug was reported by Florin Iucha (on lkml!) on Saturday. It has only
just been debugged, and I was in fact in the middle of marshalling the
fixes.
> This five-week-old diff only ever appeared in 2.6.21-mm1, which was
> released four days ago. It was then whizzed into mainline. We thus lost
> five weeks public testing which would probably have saved Jeff his pain.
>
> What went wrong?
Probably my fault. I've had a couple of weeks of heavy travel due to
various circumstances that were beyond my control, and so I had little
time in which to test the stuff and push it out.
Another factor that is affecting us is the slow but gradual collapse of
the OSDL NFSv4 regression testing effort.
Trond
next prev parent reply other threads:[~2007-05-10 0:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 21:30 Jeff Garzik
2007-05-09 21:51 ` Linus Torvalds
2007-05-09 22:17 ` Trond Myklebust
2007-05-09 22:48 ` Jeff Garzik
2007-05-09 22:03 ` Trond Myklebust
2007-05-09 22:52 ` Andrew Morton
2007-05-10 0:10 ` Trond Myklebust [this message]
2007-05-10 13:36 ` Chuck Lever
2007-05-11 22:54 ` Jeff Garzik
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=1178755813.6760.26.camel@heimdal.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@stusta.de \
--cc=chuck.lever@oracle.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=torvalds@linux-foundation.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®