From: Jim Rees <rees@umich.edu>
To: NeilBrown <neilb@suse.de>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Charles Edward Lever <chuck.lever@oracle.com>
Subject: Re: please proof-read: updates to nfs.man for some missing options.
Date: Wed, 13 Nov 2013 22:12:53 -0500 [thread overview]
Message-ID: <20131114031253.GA9522@umich.edu> (raw)
In-Reply-To: <20131114140244.6f7c0094@notabene.brown>
NeilBrown wrote:
+.BR addr= ip-address
+This option is rarely used but can provide an explicit IP address of
+the NFS server in cases where the server is multi-homed.
+.TP 1.5i
I would change "rarely used" to "usually not needed." Also I think you have
this option in here twice.
next prev parent reply other threads:[~2013-11-14 3:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 3:02 please proof-read: updates to nfs.man for some missing options NeilBrown
2013-11-14 3:11 ` Chuck Lever
2013-11-14 3:33 ` NeilBrown
2013-11-14 3:12 ` Jim Rees [this message]
2013-11-14 3:13 ` Chuck Lever
2013-11-14 3:25 ` NeilBrown
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=20131114031253.GA9522@umich.edu \
--to=rees@umich.edu \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
/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).