From: Warren Toomey <wkt@tuhs.org>
To: tuhs@tuhs.org
Subject: [TUHS] Moderation on for a bit
Date: Sat, 30 Jun 2018 10:21:12 +1000 [thread overview]
Message-ID: <20180630002112.GA17705@minnie.tuhs.org> (raw)
OK, so now I'm a bit p*ssed off. We've losy Johnny a few days ago because of
the traffic on the list and now Tim is asking to be unsubscribed.
First up: Unix Heritage. I don't mind a bit of drift but seriously?! I
put in a nugde to wind up the comp.arch chat but that didn't help.
Secondly: a few of you need to pull your heads in.
The TUHS list is going to be moderated for the next couple of days. If you
really feel it necessary, you can post a _summary_ of your comp.arch position
and then stop.
Posts on Unix anecdotes and on-topic stuff I will let through.
Cheers, Warren
next reply other threads:[~2018-06-30 0:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-30 0:21 Warren Toomey [this message]
2018-06-30 1:18 ` Larry McVoy
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=20180630002112.GA17705@minnie.tuhs.org \
--to=wkt@tuhs.org \
--cc=tuhs@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).