From: Martin C.Atkins <martin@parvat.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Distributed filesystems: Plan 9 vs. Linux
Date: Tue, 2 Mar 2004 09:40:53 +0530 [thread overview]
Message-ID: <20040302094053.0e2f265a.martin@parvat.com> (raw)
In-Reply-To: <33c750f587189dcfaf9b67aa46ab0365@juice.thebigchoice.com>
On Mon, 1 Mar 2004 17:37:18 0000 matt@proweb.co.uk wrote:
> I have quite a bit of 9p (client & server) done in python if that interests anyone
>
> m
>
I've got Russ' 9p Python code. It was very nice, but it would be interesting to see
some other approaches to compare...
Thanks,
Martin
--
Martin C. Atkins martin@parvat.com
Parvat Infotech Private Limited http://www.parvat.com{/,/martin}
next prev parent reply other threads:[~2004-03-02 4:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-29 19:59 John E. Barham
2004-02-29 19:38 ` andrey mirtchovski
2004-02-29 23:32 ` boyd, rounin
2004-03-01 17:27 ` John E. Barham
2004-03-01 17:37 ` matt
2004-03-02 4:10 ` Martin C.Atkins [this message]
2004-02-29 20:26 ` Jeff Sickel
2004-03-01 17:14 ` John E. Barham
2004-03-01 18:26 ` Jeff Sickel
2004-03-01 1:56 ` James Horey
2004-03-01 2:04 ` Geoff Collyer
2004-03-03 7:46 YAMANASHI Takeshi
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=20040302094053.0e2f265a.martin@parvat.com \
--to=martin@parvat.com \
--cc=9fans@cse.psu.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).