From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jim Rees <rees@umich.edu>
Cc: Kevin Coffman <kwc@umich.edu>,
NFS list <linux-nfs@vger.kernel.org>,
Steve Dickson <SteveD@redhat.com>
Subject: Re: RFC: Handling GSS rotated data
Date: Thu, 12 Apr 2012 12:46:36 -0400 [thread overview]
Message-ID: <20120412164636.GA4684@fieldses.org> (raw)
In-Reply-To: <20120412010656.GA18591@umich.edu>
On Wed, Apr 11, 2012 at 09:06:56PM -0400, Jim Rees wrote:
> J. Bruce Fields wrote:
>
> + * without using two much stack space.
>
> "two" should be "too".
>
> Sorry to violate the nfs list convention of quoting the entire patch in my
> reply but it seems unnecessary in this case.
We'll refer your case to the local netiquette committee for a judgement.
--b.
prev parent reply other threads:[~2012-04-12 16:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 22:28 RFC: Handling GSS rotated data Kevin Coffman
2012-04-10 21:56 ` J. Bruce Fields
2012-04-10 23:02 ` J. Bruce Fields
2012-04-11 0:56 ` Kevin Coffman
2012-04-12 0:12 ` J. Bruce Fields
2012-04-12 0:19 ` J. Bruce Fields
2012-05-01 23:52 ` J. Bruce Fields
2012-05-02 22:08 ` J. Bruce Fields
2012-04-12 1:06 ` Jim Rees
2012-04-12 16:46 ` J. Bruce Fields [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=20120412164636.GA4684@fieldses.org \
--to=bfields@fieldses.org \
--cc=SteveD@redhat.com \
--cc=kwc@umich.edu \
--cc=linux-nfs@vger.kernel.org \
--cc=rees@umich.edu \
/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).