From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] grrrr
Date: Fri, 15 Jun 2001 14:44:24 +0100 [thread overview]
Message-ID: <20010615133553.F3AF819A23@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 45 bytes --]
well, you're our resident plan9 sniper...
[-- Attachment #2: Type: message/rfc822, Size: 1764 bytes --]
To: <cse.psu.edu!9fans>
Subject: Re: [9fans] grrrr
Date: Fri, 15 Jun 2001 14:14:40 +0200
Message-ID: <0bba01c0f594$c0f2dac0$e8b7c6d4@SOMA>
snipers, that's what you need -- snipers.
next reply other threads:[~2001-06-15 13:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-15 13:44 rog [this message]
2001-06-15 18:26 ` Boyd Roberts
-- strict thread matches above, loose matches on Subject: below --
2001-06-16 1:06 Scott Schwartz
2001-06-16 0:50 dmr
2001-06-15 11:16 Laura Creighton
2001-06-15 11:19 ` Laura Creighton
2001-06-15 12:14 ` Boyd Roberts
2001-06-15 20:49 ` randolph
2001-06-15 21:31 ` Boyd Roberts
2001-06-15 23:16 ` Sam Ducksworth
2001-06-15 23:39 ` Boyd Roberts
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=20010615133553.F3AF819A23@mail.cse.psu.edu \
--to=rog@vitanuova.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).