From: Christoph Hellwig <hch@infradead.org>
To: ericvh@gmail.com
Cc: linux-kernel@vger.kernel.org,
v9fs-developer@lists.sourceforge.net, akpm@osdl.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2.6.13-rc3-mm2] v9fs: add fd based transport
Date: Thu, 28 Jul 2005 15:17:49 +0100 [thread overview]
Message-ID: <20050728141749.GB22173@infradead.org> (raw)
In-Reply-To: <200507281358.j6SDwBRZ026263@ms-smtp-03-eri0.texas.rr.com>
On Thu, Jul 28, 2005 at 08:57:23AM -0500, ericvh@gmail.com wrote:
> v9fs: add file-descriptor based transport as was requested by LANL and
> Plan 9 from User Space folks.
Couldn't the two other transports be implemented ontop of this one using
a mount helper doing the pipe or tcp setup?
next prev parent reply other threads:[~2005-07-28 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 13:57 [PATCH 2.6.13-rc3-mm2] v9fs: add fd based transport ericvh
2005-07-28 14:17 ` Christoph Hellwig [this message]
2005-07-28 14:19 ` [V9fs-developer] " Ronald G. Minnich
2005-07-28 18:14 ` Eric Van Hensbergen
2005-07-28 14:38 ` [V9fs-developer] " Russ Cox
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=20050728141749.GB22173@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=ericvh@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=v9fs-developer@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).