From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: RE: [9fans] A quite amusing thing...
Date: Sat, 22 Feb 2003 15:40:39 -0500 [thread overview]
Message-ID: <dd2476bd28fdd047b599c7529c33c089@plan9.bell-labs.com> (raw)
In-Reply-To: <A53BD906DDC06E489581B67EA300F008020F9D@mobydick.int.entrisphere.com>
> Leendert van Doorn was a summer student at the labs that year I think
That's part of what was amusing, though the users file seems
to indicate it was 1995.
The Amoeba pit.c code as he left it when the project ended
still didn't have the AAM loop though -- the FSD guys added it.
Russ
next prev parent reply other threads:[~2003-02-22 20:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-22 20:34 philw
2003-02-22 20:40 ` Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-22 19:17 Maksim Radziwill
2003-02-22 20:30 ` Russ Cox
2003-02-22 20:51 ` David Presotto
2003-02-23 2:16 ` Skip Tavakkolian
2003-02-23 3:53 ` John Packer
2003-02-23 6:10 ` northern snowfall
2003-02-23 8:30 ` John Packer
2003-02-23 20:26 ` northern snowfall
2003-02-23 21:28 ` John Packer
2003-02-23 22:00 ` northern snowfall
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=dd2476bd28fdd047b599c7529c33c089@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).