linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Filz <ffilz-lists@mindspring.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Frank Filz <ffilz-lists@mindspring.com>,
	Linux NFS Mailing list <linux-nfs@vger.kernel.org>,
	"J. Bruce Fields" <bfields@redhat.com>,
	ffilz@us.ibm.com
Subject: Re: Some pynfs updates
Date: Tue, 11 Jun 2013 13:22:46 -0700	[thread overview]
Message-ID: <51B78716.30703@mindspring.com> (raw)
In-Reply-To: <20130611200610.GB29634@fieldses.org>

On 06/11/2013 01:06 PM, J. Bruce Fields wrote:
> On Tue, Jun 11, 2013 at 10:08:09AM -0700, Frank Filz wrote:
>> Please pull this branch from github:
>> https://github.com/ffilz/pynfs/commits/master
>
> Thanks, applied (actually from git://github.com/ffilz/pynfs.git master).
>
>> commit a6548ab80a68787dc3fcb5c8531d4d189d77c3a9
>> Author: Frank S. Filz <ffilz@us.ibm.com>
>> Date:   Wed May 1 16:06:56 2013 -0700
>>
>> Make mode 000 tests expect NFS4_OK when run as root
>>
>> They will warn if NFS4ERR_ACCESS is returned.
>
> ... though I'm not sure about this one.  root-squashing is completely
> normal, I'm not convinced it merits a warning.

Oh, didn't think about that, good point. Would you like me to submit a 
patch to make it an acceptable return?

Frank



  reply	other threads:[~2013-06-11 20:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-11 17:08 Some pynfs updates Frank Filz
2013-06-11 20:06 ` J. Bruce Fields
2013-06-11 20:22   ` Frank Filz [this message]
2013-06-11 20:28     ` J. Bruce Fields
2013-06-11 21:01       ` Frank Filz
2013-06-11 21:01         ` J. Bruce Fields

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=51B78716.30703@mindspring.com \
    --to=ffilz-lists@mindspring.com \
    --cc=bfields@fieldses.org \
    --cc=bfields@redhat.com \
    --cc=ffilz@us.ibm.com \
    --cc=linux-nfs@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).