Linux NFS development
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org, Thomas.Talpey@netapp.com
Subject: Re: [PATCH] nfs(5): Clarify behavior of the mountproto= and proto= options
Date: Wed, 08 Oct 2008 10:58:56 -0400	[thread overview]
Message-ID: <48ECCAB0.7080102@RedHat.com> (raw)
In-Reply-To: <20081002155516.25702.69105.stgit-meopP2rzCrTwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>



Chuck Lever wrote:
> Document the interaction between the mountproto= and the proto= mount
> options in a new subsection of nfs(5).
> 
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
Committed...

steved

      parent reply	other threads:[~2008-10-08 15:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-02 15:56 [PATCH] nfs(5): Clarify behavior of the mountproto= and proto= options Chuck Lever
     [not found] ` <20081002155516.25702.69105.stgit-meopP2rzCrTwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2008-10-08 14:58   ` Steve Dickson [this message]

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=48ECCAB0.7080102@RedHat.com \
    --to=steved@redhat.com \
    --cc=Thomas.Talpey@netapp.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.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