From: Richard Ems <Richard.Ems@cape-horn-eng.com>
To: markgw@sgi.com
Cc: Russell Cattelan <cattelan@thebarn.com>,
xfs@oss.sgi.com, Bill O'Donnell <billodo@sgi.com>
Subject: Re: XFS internal error xfs_btree_check_lblock
Date: Tue, 22 Jul 2008 12:49:18 +0200 [thread overview]
Message-ID: <4885BB2E.3010508@cape-horn-eng.com> (raw)
In-Reply-To: <488552EC.8060803@sgi.com>
Mark Goodwin wrote:
> Some of the above might not refer directly to the final committed
> patches but the thread URLs should be accurate. These are bug fixes
> that go a long way back and really do need to be back-ported and
> pushed out for the mentioned distros. There are probably other patches
> not listed above that should be considered too.
Hi Mark, thanks for the list and clarifications.
But still some more questions ... who does the backporting for the
distros? SGI or the distros themselves?
Is someone from Novell / SUSE / openSUSE reading here?
When can we *expect* to have these patches backported? In one month?
Three months? More?
Thanks, Richard
--
Richard Ems mail: Richard.Ems@Cape-Horn-Eng.com
Cape Horn Engineering S.L.
C/ Dr. J.J. Dómine 1, 5º piso
46011 Valencia
Tel : +34 96 3242923 / Fax 924
next prev parent reply other threads:[~2008-07-22 10:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 14:55 XFS internal error xfs_btree_check_lblock Richard Ems
2008-07-19 3:08 ` Mark Goodwin
2008-07-19 16:36 ` sandeen
2008-07-21 9:33 ` Richard Ems
2008-07-21 16:11 ` Eric Sandeen
2008-07-21 23:40 ` Mark Goodwin
2008-07-22 2:07 ` Eric Sandeen
2008-07-21 16:06 ` Russell Cattelan
2008-07-22 3:24 ` Mark Goodwin
2008-07-22 10:49 ` Richard Ems [this message]
2008-07-22 11:27 ` Mark Goodwin
2008-07-22 15:22 ` Eric Sandeen
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=4885BB2E.3010508@cape-horn-eng.com \
--to=richard.ems@cape-horn-eng.com \
--cc=billodo@sgi.com \
--cc=cattelan@thebarn.com \
--cc=markgw@sgi.com \
--cc=xfs@oss.sgi.com \
/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