From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] pic generators?
Date: Wed, 5 Feb 2003 11:36:57 -0500 [thread overview]
Message-ID: <0b12a61bf26fe4edb12a347ae0220b86@plan9.bell-labs.com> (raw)
In-Reply-To: <c80f9308f388c7157ad88cea2c90be6b@vitanuova.com>
9trouble is the general everything address.
next prev parent reply other threads:[~2003-02-05 16:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 16:36 rog
2003-02-05 16:36 ` Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-06 0:46 okamoto
2003-02-05 14:59 Sam
2003-02-05 15:05 ` Fco.J.Ballesteros
2003-02-05 15:11 ` Sam
2003-02-05 15:15 ` Fco.J.Ballesteros
2003-02-05 15:54 ` Boyd Roberts
2003-02-05 17:01 ` Charles Forsyth
2003-02-05 15:59 ` Russ Cox
2003-02-05 20:23 ` William Josephson
2003-02-06 9:40 ` Douglas A. Gwyn
2003-02-05 15:38 ` David Butler
2003-02-05 16:31 ` Jon Snader
2003-02-06 12:52 ` Aharon Robbins
2003-02-07 12:33 ` Ralph Corderoy
2003-02-05 17:05 ` Skip Tavakkolian
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=0b12a61bf26fe4edb12a347ae0220b86@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).