From: "J. Bruce Fields" <bfields@fieldses.org>
To: "cyril.lacabanne" <cyril.lacabanne@bull.net>
Cc: nfsv4@linux-nfs.org, ltp-list@lists.sourceforge.net,
nfs@lists.sourceforge.net, libtirpc-devel@lists.sourceforge.net
Subject: Re: RPC and TI-RPC Tests Suite
Date: Fri, 25 May 2007 21:10:06 -0400 [thread overview]
Message-ID: <20070526011006.GI32073@fieldses.org> (raw)
In-Reply-To: <4651BBF8.4040008@bull.net>
On Mon, May 21, 2007 at 05:34:16PM +0200, cyril.lacabanne wrote:
...
> comments : version 1.2 (2007-05-15), 10 pages
...
> comments : version 1.3 (2007-05-15), 138 pages
>
> I have already started writing the test suite code.
> Feel free to send your remarks and comments about the design of the test
> suite !
That's a lot of pages! Is there anything in particular you're looking
for comments on?
--b.
prev parent reply other threads:[~2007-05-26 1:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 15:34 RPC and TI-RPC Tests Suite cyril.lacabanne
2007-05-26 1:10 ` J. Bruce Fields [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=20070526011006.GI32073@fieldses.org \
--to=bfields@fieldses.org \
--cc=cyril.lacabanne@bull.net \
--cc=libtirpc-devel@lists.sourceforge.net \
--cc=ltp-list@lists.sourceforge.net \
--cc=nfs@lists.sourceforge.net \
--cc=nfsv4@linux-nfs.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