From: Neil Brown <neilb@suse.de>
To: chuck.lever@oracle.com
Cc: nfs@lists.sourceforge.net, Steve Dickson <SteveD@redhat.com>
Subject: Re: [PATCH nfs-utils 1/3] probe_port should not try other versions in a version was explicitly given.
Date: Fri, 2 Nov 2007 13:02:14 +1100 [thread overview]
Message-ID: <18218.34086.347685.663123@notabene.brown> (raw)
In-Reply-To: message from Chuck Lever on Thursday November 1
On Thursday November 1, chuck.lever@oracle.com wrote:
>
> Time to add another case to our list of regression tests.
>
What! What a list of regression tests for nfs-utils (or even NFS in
general?). That would be awesome.
NeilBrown
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-11-02 2:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 5:26 [PATCH nfs-utils] probe_port should not try other versions in a version was explicitly given Neil Brown
2007-11-01 5:26 ` [PATCH nfs-utils 1/3] " Neil Brown
2007-11-01 5:26 ` [PATCH nfs-utils 2/3] Correctly probe mount v2 Neil Brown
2007-11-01 5:26 ` [PATCH nfs-utils 3/3] Fix bug in auto-exporting subordinate mounts Neil Brown
2007-11-05 9:54 ` Steve Dickson
2007-11-05 10:58 ` [PATCH nfs-utils 2/3] Correctly probe mount v2 Steve Dickson
2007-11-05 18:01 ` Peter Staubach
2007-11-01 16:29 ` [PATCH nfs-utils 1/3] probe_port should not try other versions in a version was explicitly given Chuck Lever
2007-11-02 2:02 ` Neil Brown [this message]
2007-11-02 17:01 ` Chuck Lever
2007-11-05 9:55 ` Steve Dickson
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=18218.34086.347685.663123@notabene.brown \
--to=neilb@suse.de \
--cc=SteveD@redhat.com \
--cc=chuck.lever@oracle.com \
--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