From: forsyth@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] T-Shirts
Date: Thu, 26 Oct 2000 11:46:21 +0100 [thread overview]
Message-ID: <20001026104316.0B0E5199D5@mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 32 bytes --]
which browser are you using?
[-- Attachment #2: Type: message/rfc822, Size: 1884 bytes --]
To: cse.psu.edu!9fans
Subject: Re: [9fans] T-Shirts
Date: Thu, 26 Oct 2000 08:40:06 GMT
Message-ID: <86bsw8smzh.fsf@gollum.esys.ca>
>>>>> "rog" == rog <rog@vitanuova.com> writes:
rog> you can order them from:
rog> http://www.vitanuova.com/plan9/tshirts.html
Beware that the secure payment server behind this (www.netbanx.com)
barfs when you submit your payment information through an HTTP
proxy. You'll have to temporarily disable any proxy your client
is using before you can complete the transaction.
--lyndon
next reply other threads:[~2000-10-26 10:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-26 10:46 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-10-24 9:43 rog
2000-10-26 8:40 ` Lyndon Nerenberg
2000-10-24 8:47 Bojan Zdravkovic
2000-10-24 11:27 ` Boyd Roberts
2000-10-25 8:29 ` brien c carr
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=20001026104316.0B0E5199D5@mail \
--to=forsyth@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).