From: steve.simon@snellwilcox.com
To: 9fans@cse.psu.edu
Subject: [9fans] u9cpu ?
Date: Tue, 1 Apr 2003 13:31:06 +0100 [thread overview]
Message-ID: <f9b166cd09867d87373a7a50b03c813e@snellwilcox.com> (raw)
Hi,
Anyone written u9cpu or is the feeling that
ssh has surplanted the need?
-Steve
next reply other threads:[~2003-04-01 12:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 12:31 steve.simon [this message]
2003-04-01 15:59 ` 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=f9b166cd09867d87373a7a50b03c813e@snellwilcox.com \
--to=steve.simon@snellwilcox.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).