From: Gabriel Barazer <gabriel@oxeva.fr>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: [PATCH] mount.nfs: Update description of clientaddr= in nfs(5)
Date: Fri, 31 Aug 2007 02:12:23 +0200 [thread overview]
Message-ID: <46D75CE7.2020605@oxeva.fr> (raw)
In-Reply-To: <20070830194810.4524.58037.stgit@monet.1015granger.net>
On 08/30/2007 9:48:10 PM +0200, Chuck Lever <chuck.lever@oracle.com> wrote:
> The description of clientaddr= in nfs(5) is out of date and omits some
> other typical reasons for using it. Let's start with this rewrite.
>
By the way, can we update the man page date show the current version
somewhere ? This is a bit disturbing to see "20 November 1993" at the
bottom of the man page, and would clear minds about the "ignored at this
time" or "not implemented yet" : does the word "currently" makes any
sense, when the only date showed is 15 years ago ?
Gabriel
-------------------------------------------------------------------------
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-08-31 0:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 19:48 [PATCH] mount.nfs: Update description of clientaddr= in nfs(5) Chuck Lever
2007-08-30 21:37 ` J. Bruce Fields
2007-08-31 0:12 ` Gabriel Barazer [this message]
2007-08-31 13:54 ` Chuck Lever
2007-08-31 1:35 ` Talpey, Thomas
2007-08-31 13:56 ` Chuck Lever
-- strict thread matches above, loose matches on Subject: below --
2007-08-31 15:15 Chuck Lever
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=46D75CE7.2020605@oxeva.fr \
--to=gabriel@oxeva.fr \
--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