From: Bruce Fields <bfields@fieldses.org>
To: Frank Filz <ffilzlnx@mindspring.com>
Cc: Kernel NFS List <linux-nfs@vger.kernel.org>,
"'Ganesha NFS List'" <nfs-ganesha-devel@lists.sourceforge.net>
Subject: Re: pynfs updates
Date: Mon, 30 Sep 2013 18:11:27 -0400 [thread overview]
Message-ID: <20130930221126.GD26382@fieldses.org> (raw)
In-Reply-To: <003301cebe09$5bf81090$13e831b0$@mindspring.com>
On Mon, Sep 30, 2013 at 02:17:43PM -0400, Frank Filz wrote:
> Bruce,
>
> Please pull the following branch that contains the pynfs updates I made at
> BAT:
>
> https://github.com/ffilz/pynfs/commits/master
Thanks! A few questions:
- "4.1 server tests: Fix some exception handling": could you
include in the changelog and explanation of what problem this
fixes? (And ditto, maybe, for the following commit?)
- "Fix SEQ9d to work in home directory instead of root": did you
intend to include the chunk in nfs4.1/nfs4lib.py? It looks
irrelevant.
- "Add two SECINFO_NO_NAME tests for SECINFO_STYLE4_PARENT":
- SECNN3: is / required to have no parent? (I'd assumed
here that it would also be OK to follow the convention
that / is its own parent, but I'll admit to not having
thought about this much.)
- SECNN4: is env.home necessarily unequal to "/"? Would
seem better to do the lookup in a subdirectory just to
be certain.
--b.
next prev parent reply other threads:[~2013-09-30 22:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 18:17 pynfs updates Frank Filz
2013-09-30 22:11 ` Bruce Fields [this message]
2013-09-30 23:54 ` Frank Filz
2013-10-01 14:26 ` 'Bruce Fields'
2013-10-01 14:30 ` 'Bruce Fields'
2013-10-01 15:42 ` Frank Filz
2013-10-01 19:05 ` Frank Filz
2013-10-02 11:36 ` 'Bruce Fields'
2013-10-02 15:58 ` Frank Filz
2013-10-01 18:21 ` Frank Filz
2013-10-01 18:45 ` '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=20130930221126.GD26382@fieldses.org \
--to=bfields@fieldses.org \
--cc=ffilzlnx@mindspring.com \
--cc=linux-nfs@vger.kernel.org \
--cc=nfs-ganesha-devel@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 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.