From: Colin DeVilbiss <crdevilb@mtu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] setup?
Date: Fri, 21 Jul 2000 11:32:38 -0400 [thread overview]
Message-ID: <20000721113238.A429@crdevilb.bresnanlink.net> (raw)
In-Reply-To: <200007211505.LAA10048@cse.psu.edu>; from rsc@plan9.bell-labs.com on Fri, Jul 21, 2000 at 11:05:08AM -0400
> I have patches to upas/fs that provide pop3 access.
> If you bug me, I'm happy to provide them.
consider yourself bugged. :)
> No one,
> to my knowledge, has done anything for nntp, although
> it's a file system just itching to be written.
hm. would this be an appropriate project for someone new to the ``plan9
way'' or is it probably too ambitious?
(I have some experience with unix sockets, but I have not written any
plan9 networking software; for that matter, s/networking //.)
--
Colin DeVilbiss
crdevilb@mtu.edu
next prev parent reply other threads:[~2000-07-21 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-21 15:05 Russ Cox
2000-07-21 15:32 ` Colin DeVilbiss [this message]
2000-07-21 16:36 ` Andrey Mirtchovski
-- strict thread matches above, loose matches on Subject: below --
2000-07-24 3:02 okamoto
2000-07-21 18:44 jmk
2000-07-21 18:19 Russ Cox
2000-07-21 1:19 Colin DeVilbiss
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=20000721113238.A429@crdevilb.bresnanlink.net \
--to=crdevilb@mtu.edu \
--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).