public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Geir A. Myrestrand" <geir.myrestrand@falconstor.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: James Pearson <james-p@moving-picture.com>, xfs@oss.sgi.com
Subject: Re: Update for the RHEL4 XFS module?
Date: Mon, 13 Nov 2006 12:47:53 -0500	[thread overview]
Message-ID: <4558AFC9.3010009@falconstor.com> (raw)
In-Reply-To: <4558AEFE.10108@sandeen.net>

Eric Sandeen wrote:
> Geir A. Myrestrand wrote:
>> Eric Sandeen wrote:
>>> James Pearson wrote:
>>>> The RHEL4 XFS module code at 
>>>> <ftp://oss.sgi.com/projects/xfs/testing/RHEL4/> is now about a year old.
>>>>
>>>> Is there any chance that it could be updated with something based on 
>>>> more recent code?
>>>>
>>> Funny you should ask, I just started looking at this last night :)
>>>
>>> It was originally based on the SLES9 xfs code; my plan is to simply 
>>> update it to the latest sles9 xfs codebase, as that has been tended to 
>>> with a goal of stability by the fine folks at sgi....  so, no 
>>> bleeding-edge xfs for now (I don't particularly want to backport 2.6.18 
>>> xfs code to 2.6.9....)
>>>
>> Eric, please notify us via the list when it has been updated.
>> I would like this module updated too...
> 
> Will do.  Are there particular issues you're having, or is your code
> just feeling a bit old in general.  ;-)

No particular issue in my case, but there tend to be some bug fixes in 
any given 12-month time-span... ;-)

-- 

Geir A. Myrestrand

      reply	other threads:[~2006-11-13 18:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-13 15:48 Update for the RHEL4 XFS module? James Pearson
2006-11-13 16:15 ` Eric Sandeen
2006-11-13 16:59   ` James Pearson
2006-11-13 17:40   ` Geir A. Myrestrand
2006-11-13 17:44     ` Eric Sandeen
2006-11-13 17:47       ` Geir A. Myrestrand [this message]

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=4558AFC9.3010009@falconstor.com \
    --to=geir.myrestrand@falconstor.com \
    --cc=james-p@moving-picture.com \
    --cc=sandeen@sandeen.net \
    --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