From: presotto@closedmind.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Tage's thesis
Date: Mon, 26 Nov 2001 15:00:58 -0500 [thread overview]
Message-ID: <20011126200059.73F3C199D7@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 44 bytes --]
No, I haven't. Go ahead and ask Leendert.
[-- Attachment #2: Type: message/rfc822, Size: 2789 bytes --]
[-- Attachment #2.1.1: Type: text/plain, Size: 51 bytes --]
Sorry, I sent that to the wrong place.
Sape
[-- Attachment #2.1.2: Type: message/rfc822, Size: 1245 bytes --]
From: Sape Mullender <sape@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: [9fans] Tage's thesis
Date: Mon, 26 Nov 2001 14:53:11 -0500
Message-ID: <20011126195313.3C760199EC@mail.cse.psu.edu>
Have you had a chance yet? If you don't have time, I'll ask Leendert.
Sape
next reply other threads:[~2001-11-26 20:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-26 20:00 presotto [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-26 19:57 Sape Mullender
2001-11-26 19:53 Sape Mullender
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=20011126200059.73F3C199D7@mail.cse.psu.edu \
--to=presotto@closedmind.org \
--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).