From: bwc@borf.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rudp
Date: Sat, 8 Sep 2001 13:52:59 -0400 [thread overview]
Message-ID: <20010908175150.15CA619A02@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 21 bytes --]
Not that I know of.
[-- Attachment #2: Type: message/rfc822, Size: 1361 bytes --]
From: Sam <sah@softcardsystems.com>
To: <9fans@cse.psu.edu>
Subject: [9fans] rudp
Date: Sat, 8 Sep 2001 11:48:10 -0400 (EDT)
Message-ID: <Pine.LNX.4.30.0109081146110.2754-100000@athena>
is there any documentation available for the p9 RUDP (snoopy -r)?
sam
next reply other threads:[~2001-09-08 17:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-08 17:52 bwc [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-15 16:55 andrey mirtchovski
2002-04-15 15:31 rog
2002-04-15 15:21 Russ Cox
2002-04-15 14:58 andrey mirtchovski
2001-09-10 1:46 presotto
[not found] <ehg@research.bell-labs.com>
2001-09-08 16:59 ` Eric Grosse
2001-09-10 1:33 ` Scott Schwartz
2001-09-10 18:58 ` Boyd Roberts
2001-09-08 15:48 Sam
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=20010908175150.15CA619A02@mail.cse.psu.edu \
--to=bwc@borf.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).