From: "boyd, rounin" <boyd@insultant.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] NAT'ing a drawterm connection
Date: Tue, 26 Aug 2003 03:50:33 +0200 [thread overview]
Message-ID: <011101c36b74$70d08d00$b9844051@insultant.net> (raw)
In-Reply-To: <d53d425f2c6d993b4f9bc262bbe6b99c@centurytel.net>
> I see your point, but, customers of a service wouldn't be sympathetic
> to that answer.
oh i agree, but, for the moment, i have nothing much to protect.
next prev parent reply other threads:[~2003-08-26 1:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-26 1:16 Skip Tavakkolian
2003-08-26 1:50 ` boyd, rounin [this message]
2003-08-26 4:25 ` Jim Choate
2003-08-26 4:17 ` Jim Choate
-- strict thread matches above, loose matches on Subject: below --
2003-08-29 4:39 YAMANASHI Takeshi
2003-08-25 4:00 Rob Ristroph
2003-08-25 4:04 ` andrey mirtchovski
2003-08-25 5:15 ` Rob Ristroph
2003-08-25 5:22 ` andrey mirtchovski
2003-08-25 5:26 ` andrey mirtchovski
2003-08-25 12:35 ` Bruce Ellis
2003-08-25 13:18 ` Russ Cox
2003-08-25 17:52 ` Bruce Ellis
2003-08-26 0:30 ` boyd, rounin
2003-08-28 3:23 ` Russ Cox
2003-08-29 4:32 ` Rob Ristroph
2003-08-29 4:50 ` andrey mirtchovski
2003-08-25 14:53 ` matt
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='011101c36b74$70d08d00$b9844051@insultant.net' \
--to=boyd@insultant.net \
--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).