From: "J. Bruce Fields" <bfields@fieldses.org>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-fsdevel@vger.kernel.org, nfs@lists.sourceforge.net,
Greg Banks <gnb@sgi.com>
Subject: Re: [PATCH] exportfs: fix doc types
Date: Fri, 14 Sep 2007 12:40:40 -0400 [thread overview]
Message-ID: <20070914164040.GC26622@fieldses.org> (raw)
In-Reply-To: <20070914160301.GA6461@lst.de>
On Fri, Sep 14, 2007 at 06:03:01PM +0200, Christoph Hellwig wrote:
> And here's a patch to fix the typos Greg found:
Thanks. I already had a couple of those in a separate patch, so I've
folded this in.
--b.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2007-09-14 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 13:17 [PATH 18/19] exportfs: update documentation Christoph Hellwig
2007-09-14 15:24 ` [NFS] " Greg Banks
2007-09-14 16:03 ` [PATCH] exportfs: fix doc types Christoph Hellwig
2007-09-14 16:40 ` 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=20070914164040.GC26622@fieldses.org \
--to=bfields@fieldses.org \
--cc=gnb@sgi.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).