From: "Chris Hollis-Locke" <chris@cjl1.demon.co.uk>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Origins of the name of 4th edition file server
Date: Fri, 17 Jan 2003 19:14:40 +0000 [thread overview]
Message-ID: <002601c2be5c$c95bcae0$2248dec2@falken> (raw)
In-Reply-To: <3E28303D.9000100@nas.com>
Jack Johnson wrote:
> Surely it would need the option to wank recursively.
I think a more Plan9 approach would be for it to mount itself.
Chris.
next prev parent reply other threads:[~2003-01-17 19:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 9:39 Andrew Simmons
2003-01-17 16:33 ` Jack Johnson
2003-01-17 16:11 ` Conor Williams
2003-01-17 19:14 ` Chris Hollis-Locke [this message]
2003-01-24 7:24 ` Tomas
2003-01-24 16:47 ` Russ Cox
2003-01-24 20:38 ` Tomas
2003-01-24 20:47 ` andrey mirtchovski
-- strict thread matches above, loose matches on Subject: below --
2003-01-18 6:04 Andrew Simmons
2003-01-15 8:12 Skip Tavakkolian
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='002601c2be5c$c95bcae0$2248dec2@falken' \
--to=chris@cjl1.demon.co.uk \
--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).