linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jim Rees <rees@umich.edu>
To: Benny Halevy <bhalevy@panasas.com>
Cc: Chuck Lever <chuck.lever@oracle.com>,
	Steve Dickson <SteveD@redhat.com>,
	linux-nfs@vger.kernel.org, peter honeyman <honey@citi.umich.edu>
Subject: Re: [PATCH] nfs-utils typo
Date: Wed, 6 Oct 2010 10:36:07 -0400	[thread overview]
Message-ID: <20101006143606.GB18235@merit.edu> (raw)
In-Reply-To: <4CAC747F.8080209@panasas.com>

Benny Halevy wrote:

  On 2010-10-05 22:34, Chuck Lever wrote:
  > negotiate(s)?
  > 
  
  We'll get it right. Eventually... ;-)

I work in the spelling department.  The grammar department is down the
hall.  Nevertheless, I have sent in a revised patch.  Glad that my trip to
Boston has been productive.

      reply	other threads:[~2010-10-06 14:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-05 19:43 [PATCH] nfs-utils typo Jim Rees
     [not found] ` <20101005194304.GA7508-8f4Pc2RrbJmHXe+LvDLADg@public.gmane.org>
2010-10-06  2:34   ` Chuck Lever
2010-10-06 13:07     ` Benny Halevy
2010-10-06 14:36       ` Jim Rees [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=20101006143606.GB18235@merit.edu \
    --to=rees@umich.edu \
    --cc=SteveD@redhat.com \
    --cc=bhalevy@panasas.com \
    --cc=chuck.lever@oracle.com \
    --cc=honey@citi.umich.edu \
    --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;
as well as URLs for NNTP newsgroup(s).