"Albert D. Cahalan" wrote:
> Hans Reiser writes:
>
> > Tell us what to code for, and so long as it doesn't involve looking
> > up files by their 32 bit inode numbers we'll probably be happy to
> > code to it. The Neil Brown stuff is already coded for though.
>
> Next time around, when you update
On Friday, May 11, 2001 04:00:20 AM -0700 Hans Reiser <[EMAIL PROTECTED]>
wrote:
> Alan Cox wrote:
>
>> > Are you referring to Neil Brown's nfs operations patch as being as
>> > ugly as hell, or something else? Just want to understand what you are
>> > saying before arguing.
>>
>> Andi h
On Friday, May 11, 2001 12:07:08 PM -0700 Hans Reiser <[EMAIL PROTECTED]>
wrote:
> "Albert D. Cahalan" wrote:
>
>> Hans Reiser writes:
>>
>> > Tell us what to code for, and so long as it doesn't involve looking
>> > up files by their 32 bit inode numbers we'll probably be happy to
>> > code t
Hans Reiser writes:
> Tell us what to code for, and so long as it doesn't involve looking
> up files by their 32 bit inode numbers we'll probably be happy to
> code to it. The Neil Brown stuff is already coded for though.
Next time around, when you update the on-disk format, how about
allowing
Alan Cox wrote:
> > Are you referring to Neil Brown's nfs operations patch as being as ugly as
> > hell, or something else? Just want to understand what you are saying before
> > arguing.
>
> Andi has sent me some stuff to look at. He listed four implementations and I've
> only seen two of t
5 matches
Mail list logo
