All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: James Pearson <james-p@moving-picture.com>
Cc: linux-nfs@vger.kernel.org, steved@redhat.com
Subject: Re: [PATCH] nfs-utils: remove possibly false statement from exports.man
Date: Wed, 22 Jun 2011 13:15:23 -0400	[thread overview]
Message-ID: <20110622171523.GA2284@fieldses.org> (raw)
In-Reply-To: <4E01CE91.50203@moving-picture.com>


Works for me, thanks.--b.

On Wed, Jun 22, 2011 at 12:14:25PM +0100, James Pearson wrote:
> A very minor change suggested by J. Bruce Fields
> <bfields@fieldses.org> to remove the statement that exporting to a
> single host or IP address is the "most common format" - as it
> probably isn't.
> 
> Signed-off-by: James Pearson <james-p@moving-picture.com>
> 
> --- a/utils/exportfs/exports.man        2011-06-22 11:37:41.228238000 +0100
> +++ b/utils/exportfs/exports.man        2011-06-22 11:38:51.012894000 +0100
> @@ -45,7 +45,7 @@
>  .SS Machine Name Formats
>  NFS clients may be specified in a number of ways:
>  .IP "single host
> -This is the most common format. You may specify a host either by an
> +You may specify a host either by an
>  abbreviated name recognized be the resolver, the fully qualified domain
>  name, or an IP address.
>  .IP "IP networks
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-06-22 17:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-22 11:14 [PATCH] nfs-utils: remove possibly false statement from exports.man James Pearson
2011-06-22 17:15 ` J. Bruce Fields [this message]
2011-06-22 22:37 ` 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=20110622171523.GA2284@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=james-p@moving-picture.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=steved@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.