From: "matt" <matt@proweb.co.uk>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] the usual...
Date: Wed, 12 Feb 2003 13:47:27 +0000 [thread overview]
Message-ID: <012401c2d29d$479f35f0$6501a8c0@kike> (raw)
In-Reply-To: <Pine.LNX.4.33.0302120653120.1222-100000@einstein.ssz.com>
> Agreed. My unhappiness is with the 'community' not individuals.
there is no community
next prev parent reply other threads:[~2003-02-12 13:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-12 5:39 Scott Schwartz
2003-02-12 5:47 ` George Michaelson
2003-02-12 6:35 ` Scott Schwartz
2003-02-12 6:43 ` George Michaelson
2003-02-12 10:56 ` Boyd Roberts
2003-02-12 18:46 ` Jack Johnson
2003-02-12 12:54 ` Jim Choate
2003-02-12 13:47 ` matt [this message]
2003-02-12 14:02 ` Boyd Roberts
2003-02-12 23:37 ` Jim Choate
2003-02-13 1:52 ` Dan Cross
2003-02-13 2:50 ` andrey mirtchovski
2003-02-12 16:20 ` Dan Cross
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='012401c2d29d$479f35f0$6501a8c0@kike' \
--to=matt@proweb.co.uk \
--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).