From: "J. Bruce Fields" <bfields@fieldses.org>
To: caiqian@redhat.com
Cc: linux-nfs@vger.kernel.org, nfsv4@linux-nfs.org,
pnfs@linux-nfs.org, James Laska <jlaska@redhat.com>
Subject: Re: [pnfs] Fedora NFSv4 Test Day
Date: Fri, 29 Jan 2010 11:42:29 -0500 [thread overview]
Message-ID: <20100129164229.GB24042@fieldses.org> (raw)
In-Reply-To: <1666074695.559241264778354166.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
On Fri, Jan 29, 2010 at 10:19:14AM -0500, caiqian@redhat.com wrote:
> Hi guys,
>
> There will be a NFS test event [1] focus on NFSv4 by default feature [2] and secure NFS in upcoming Fedora 13 next Thursday - 4th Feb. While we are still trying to finalize a few details there, your suggestion on other testing areas for NFS are also welcome. We are trying to make the tests as easy to follow, and provide Fedora LiveCD images during the event if possible. We will guide you and answer questions you have during the event on IRC freenode -> #fedora-test-day.
Note on https://fedoraproject.org/wiki/QA:Testcase_nfs_pynfs there seems
to be a mix-up between pynfs and connectathon instructions.
--b.
>
> Looking forwards to see you there!
> CAI Qian
>
> [1] https://fedoraproject.org/wiki/Test_Day:2010-02-04_NFS
> [2] https://fedoraproject.org/wiki/Features/NFSv4Default
> _______________________________________________
> pNFS mailing list
> pNFS@linux-nfs.org
> http://linux-nfs.org/cgi-bin/mailman/listinfo/pnfs
next prev parent reply other threads:[~2010-01-29 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <803354499.556481264778096200.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-01-29 15:19 ` Fedora NFSv4 Test Day caiqian
2010-01-29 16:42 ` J. Bruce Fields [this message]
2010-01-30 3:48 ` [pnfs] " CAI Qian
[not found] ` <1666074695.559241264778354166.JavaMail.root-k5qu2F3t005+R5eDjrG6zsCp5Q1pQRjfhaY/URYTgi6ny3qCrzbmXA@public.gmane.org>
2010-02-04 15:07 ` CAI Qian
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=20100129164229.GB24042@fieldses.org \
--to=bfields@fieldses.org \
--cc=caiqian@redhat.com \
--cc=jlaska@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=nfsv4@linux-nfs.org \
--cc=pnfs@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