From: northern snowfall <dbailey27@ameritech.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] VMware Ethernet
Date: Tue, 6 May 2003 23:59:00 -0500 [thread overview]
Message-ID: <3EB89294.8040906@ameritech.net> (raw)
In-Reply-To: <43322bde940034988285697c300aba79@plan9.bell-labs.com>
>
>
>If they're worried about posting to 9fans
>perhaps they wouldn't mind mailing 9trouble,
>which is explicitly for installation problems,
>among other things.
>
I actually mention 9trouble, too. I just can't monitor
it to see who actually posts (obviously). I guess it
just boils down to a choice of fear versus determination
to learn/get involved.
Don
>
next prev parent reply other threads:[~2003-05-07 4:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-07 3:40 northern snowfall
2003-05-07 3:16 ` ron minnich
2003-05-07 3:31 ` Russ Cox
2003-05-07 3:33 ` Russ Cox
2003-05-07 4:44 ` northern snowfall
2003-05-07 3:49 ` Russ Cox
2003-05-07 4:59 ` northern snowfall [this message]
2003-05-07 9:16 ` paurea
2003-05-07 9:21 ` paurea
2003-05-07 14:41 ` ron minnich
2003-05-07 14:54 ` Russ Cox
-- strict thread matches above, loose matches on Subject: below --
2001-10-03 16:16 [9fans] VMware ethernet Russ Cox
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=3EB89294.8040906@ameritech.net \
--to=dbailey27@ameritech.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).