xfs
[Top] [All Lists]

Re: Who do I talk to contribute?

To: Daniel Moore <dxm@xxxxxxxxxxxxxxxxxxxxxxxx>, William L Jones <jones@xxxxxxxxxxxxxxxxxx>
Subject: Re: Who do I talk to contribute?
From: "Nathan Scott" <nathans@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 18 Jul 2000 14:54:07 -0500
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: Daniel Moore <dxm@clouds> "Re: Who do I talk to contribute?" (Jul 18, 1:23pm)
References: <200007180318.NAA02682@clouds.melbourne.sgi.com>
Sender: owner-linux-xfs@xxxxxxxxxxx
hi,

On Jul 18,  1:23pm, Daniel Moore wrote:
> Subject: Re: Who do I talk to contribute?
> 
> William L Jones writes:
> 
>  => I would like to contribute to the effort.   I could work on the fsr port. 
>  => Which means I probaly should do the "Finish the implementing the syssgi() 
>  => command" work item first if it is not alrady taken.
> 
> Just as an aside:
> 
> Most of the XFS specific syssgi calls are already available through ioctls,
> and the remaining growfs specific calls are in-progress in our group.
> 

There are XFS syssgi's which have not been ported as yet, e.g. the
SGI_FS_SWAPEXT syssgi call which fsr_xfs uses.  We (the Aussies)
haven't started looking into this yet.

The folk in Eagan will be best to get things rolling on this one
since (I think?) they wrote that code originally & know it best
(is that right?).

It would be a relatively simple exercise for me to get the fsr
code compiling initially and checked in with the other user tools
(which I don't mind doing if noone else jumps on it).  However, I
don't know the code at all, so I wouldn't be the best person to
handle merging of patches back into the tree & I'm unsure how much
of the kernel side of things is in place in the current Linux
code... (?)

cheers.

-- 
Nathan

<Prev in Thread] Current Thread [Next in Thread>