From: wkt@tuhs.org (Warren Toomey)
Subject: [TUHS] Unfortunately, time to limit things
Date: Mon, 6 Mar 2017 10:52:39 +1000 [thread overview]
Message-ID: <20170306005239.GA17062@minnie.tuhs.org> (raw)
All, I've been running the TUHS list since 1994 and it's always been an
open list. People can say what they want, and I rely on sense and courtesy
to ensure good behaviour. I think only once before I've had to hold and vet
an individual's postings.
However, I've seen undesirable behaviour recently on the list and I've had
a substantial amount of private correspondance about it. Therefore, I've
decided to hold and vet the postings of a few list members (i.e. >1).
I don't take this step lightly; in fact, I've dithered for a while on this.
But the new policy is: if you don't show respect to other members on the
TUHS list, I will hold and vet your postings. If your postings are respectful
then there will be no hold and vet.
I will e-mail the people involved. I feel disappointed to have taken this
step, but that's the way it is.
Cheers, Warren
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170306/a4d9a7ac/attachment.sig>
next reply other threads:[~2017-03-06 0:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 0:52 Warren Toomey [this message]
2017-03-06 7:43 ` Mutiny
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=20170306005239.GA17062@minnie.tuhs.org \
--to=wkt@tuhs.org \
/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).