From: Steve Dickson <SteveD@redhat.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Neil Brown <neilb@suse.de>, nfs@lists.sourceforge.net
Subject: Re: [Fwd: Re: [PATCH] NFS: Sign Extentions with Tru64 FSIDs.]
Date: Mon, 19 Mar 2007 11:58:14 -0400 [thread overview]
Message-ID: <45FEB316.6000102@RedHat.com> (raw)
In-Reply-To: <1174316909.6461.17.camel@heimdal.trondhjem.org>
Trond Myklebust wrote:
> On Mon, 2007-03-19 at 09:05 -0400, Steve Dickson wrote:
>> Neil Brown wrote:
>>> On Friday March 16, SteveD@redhat.com wrote:
>>>> Any status or hope with these patches??
>>> I have no problem with the nfs-utils patch though obviously I won't
>>> commit it until Trond indicates that he will accept the fs/nfs patch.
>> Sounds reasonable...
>>
>> Trond, any interest in the 4 line patch that would
>> enable turning off readdirplus? The Tru64 folks would
>> definitely appreciate it.. ;-)
>
> Fine by me, but I'm curious as to why you're not doing the same for
> NFSv4?
Cool... In this particular case, Tru64 does not support v4 so I
didn't think it was needed...
steved.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2007-03-19 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-16 15:36 [Fwd: Re: [PATCH] NFS: Sign Extentions with Tru64 FSIDs.] Steve Dickson
2007-03-18 23:43 ` Neil Brown
2007-03-19 13:05 ` Steve Dickson
2007-03-19 15:08 ` Trond Myklebust
2007-03-19 15:58 ` Steve Dickson [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=45FEB316.6000102@RedHat.com \
--to=steved@redhat.com \
--cc=Trond.Myklebust@netapp.com \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
/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