From: bs <this@invalid.address.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Python 2.2c1 on Plan 9 release 3
Date: Mon, 28 Jan 2002 11:13:39 +0000 [thread overview]
Message-ID: <3C532CC9.A1F13BF1@invalid.address.com> (raw)
In-Reply-To: <3C51A618.6EEE9EF@strakt.com>
Awesome!
Boyd Roberts wrote:
>
> With some help from Russ I seem to built one.
>
> I haven't run the tests yet, but it seems to
> function and hasn't gone 'broke' yet.
prev parent reply other threads:[~2002-01-28 11:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-25 18:38 Boyd Roberts
2002-01-28 11:13 ` bs [this message]
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=3C532CC9.A1F13BF1@invalid.address.com \
--to=this@invalid.address.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).