From: Skip Tavakkolian <9nut@9netics.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Japanese "9fans" mailing list established.
Date: Thu, 4 Nov 2004 17:25:46 -0800 [thread overview]
Message-ID: <d2875d341c51df31f0e8f067ba02152f@9netics.com> (raw)
In-Reply-To: <e58997a6e87a14f5de7ece6c261b0f1c@granite.cias.osakafu-u.ac.jp>
> we lost Ken
Did we ever have Ken?
At any rate, we can still read Ken.
Also, I agree spliting 9fans is not a good thing.
next prev parent reply other threads:[~2004-11-05 1:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 8:28 YAMANASHI Takeshi
2004-11-04 8:47 ` Kenji Okamoto
2004-11-04 9:25 ` arisawa
2004-11-05 1:12 ` Kenji Okamoto
2004-11-05 1:12 ` boyd, rounin
2004-11-05 1:25 ` Skip Tavakkolian [this message]
2004-11-05 1:29 ` Kenji Okamoto
-- strict thread matches above, loose matches on Subject: below --
2004-11-05 1:30 YAMANASHI Takeshi
2004-11-05 1:30 ` boyd, rounin
2004-11-05 1:38 ` Kenji Okamoto
2004-11-05 1:39 ` boyd, rounin
[not found] <32a656c204110323532855da1e@mail.gmail.com>
2004-11-04 8:24 ` Kenji Okamoto
2004-11-04 4:35 Vester Thacker
2004-11-04 6:04 ` Kenji Okamoto
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=d2875d341c51df31f0e8f067ba02152f@9netics.com \
--to=9nut@9netics.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).