From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] How do I
Date: Sat, 14 Jul 2001 19:16:53 +0100 [thread overview]
Message-ID: <20010714182119.3988A199C1@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 15 bytes --]
man 4 agent
[-- Attachment #2: Type: message/rfc822, Size: 1632 bytes --]
From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] How do I
Date: Sat, 14 Jul 2001 09:10:36 -0400
Message-ID: <20010714131037.BFE14199C1@mail.cse.psu.edu>
No, it's something russ cox did to get upas/fs to call up
a pop3 server. You also need to be running his authentication
client agent, the name escapes me at the moment. I'm going to
build the same function into an auth agent I'm currently
building for 9P2000. Mail rsc for details.
next reply other threads:[~2001-07-14 18:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-14 18:16 forsyth [this message]
2001-07-14 19:14 ` Michael Grunditz
-- strict thread matches above, loose matches on Subject: below --
2001-07-14 13:10 presotto
2001-07-14 13:37 ` Michael Grunditz
2001-07-13 20:06 Michael Grunditz
2001-07-14 1:19 ` Boyd Roberts
2001-07-14 7:00 ` Michael Grunditz
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=20010714182119.3988A199C1@mail.cse.psu.edu \
--to=forsyth@caldo.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).