From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: erik quanstrom <quanstro@speakeasy.net>,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] upas/fs -f /imap/...
Date: Sun, 27 Nov 2005 18:19:34 -0800 [thread overview]
Message-ID: <E1B0A227-C97E-481B-9689-77EF36F678B3@orthanc.ca> (raw)
In-Reply-To: <20051128013211.3FDEBDA182@dexter-peak.quanstro.net>
On Nov 27, 2005, at 5:32 PM, erik quanstrom wrote:
> uh, if you'd read the thread, you'd understand that you've made my
> point for me.
Smartass. Your message was phrased such that it looked like you were
still asking for confirmation. I apologize for trying to lend
assistance to an apparent request for some.
--lyndon
next prev parent reply other threads:[~2005-11-28 2:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <37dce6ddf2e5cbefbf8a246e9a19664f@proxima.alt.za>
2005-11-26 20:48 ` erik quanstrom
2005-11-27 23:40 ` Lyndon Nerenberg
2005-11-28 1:32 ` erik quanstrom
2005-11-28 2:19 ` Lyndon Nerenberg [this message]
2005-11-28 2:41 ` erik quanstrom
2005-11-28 3:06 ` Lyndon Nerenberg
2005-11-28 3:12 ` Russ Cox
2005-11-28 11:14 ` erik quanstrom
2005-11-15 4:03 erik quanstrom
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=E1B0A227-C97E-481B-9689-77EF36F678B3@orthanc.ca \
--to=lyndon@orthanc.ca \
--cc=9fans@cse.psu.edu \
--cc=quanstro@speakeasy.net \
/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).