From: Niv Sardi <xaiki@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Gary Lowell <glowell@sonic.net>, markgw@sgi.com, xfs@oss.sgi.com
Subject: Re: DMAPI JFS bug fixes
Date: Wed, 04 Jun 2008 16:11:09 +1000 [thread overview]
Message-ID: <nccwsl5rapu.fsf@sgi.com> (raw)
In-Reply-To: <4846005B.6090907@sandeen.net> (Eric Sandeen's message of "Tue, 03 Jun 2008 21:39:23 -0500")
Eric Sandeen <sandeen@sandeen.net> writes:
> Niv Sardi wrote:
>> Gary Lowell <glowell@sonic.net> writes:
>>> On May 27, 2008, at 2:50 PM, Mark Goodwin wrote:
>>>> Gary Lowell wrote:
>>>>> Hi -
>>>>> The JFS version of DMAPI had a handful of bug fixes that don't seem
>>>>> to be in the current tree. I couldn't find anything in the list
>>>>> archive about them. Would there be any interest in applying those
>>>>> fixes or is DMAPI pretty much dead ?
>>>> no it's not dead :)
>>>>
>>>>> If there is interest, I've got a patch.
>>>> yes please post it here, with due reference to the original author(s).
>>>>
>>>> Thanks
>>> Great. I'll double check that they still work with TOT and post them.
>>
>> And i thought JFS was dead =)
>>
>> any patch would do, I've been looking around and couldn't really find a
>> repository of the JFS/DMAPI changes. did you find anything like that ?
^^^^^^^^^^
> didja google for "jfs dmapi? ;)
>
> http://jfs.sourceforge.net/project/pub/dmapi/
>
> sorting out fixes from that looks like fun though.
That's exactly why the key word here was repository, I really didn't
think I'd bother to even look at a website that still had frames in 2008
=)
Cheers,
--
Niv Sardi
prev parent reply other threads:[~2008-06-04 6:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 21:10 DMAPI JFS bug fixes Gary Lowell
2008-05-27 21:50 ` Mark Goodwin
2008-05-30 2:16 ` Gary Lowell
2008-06-04 0:57 ` Niv Sardi
2008-06-04 2:39 ` Eric Sandeen
2008-06-04 6:11 ` Niv Sardi [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=nccwsl5rapu.fsf@sgi.com \
--to=xaiki@sgi.com \
--cc=glowell@sonic.net \
--cc=markgw@sgi.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 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.