From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] OK, time to step back from the keyboard (for a bit)
Date: Thu, 5 Jan 2017 14:37:17 +1100 [thread overview]
Message-ID: <20170105033717.GD99823@eureka.lemis.com> (raw)
In-Reply-To: <20170104201721.GA13719@minnie.tuhs.org>
On Thursday, 5 January 2017 at 6:17:21 +1000, Warren Toomey wrote:
> Goodness, I go to sleep, wake up 8 hours later and there's 50 messages in
> the TUHS mailing list. Some of these do relate to the history of Unix, but
> some are getting quite off-topic.
>
> So, can I get you all to just pause before you send in a reply and ask:
> is this really relevant to the history of Unix, and does it contribute
> in a meaningful way to the conversation.
Is this really necessary? There's a certain amount of traffic
necessary to keep a list going, and restricting it can have unwanted
results. Yes, I agree, there's a lot of traffic at the moment, and
I'm having trouble with it too, but it'll subside of its own accord.
And who knows, maybe some unexpected gem might pop up.
Greg
--
Sent from my desktop computer.
Finger grog at FreeBSD.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170105/f65e736d/attachment.sig>
prev parent reply other threads:[~2017-01-05 3:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 20:17 Warren Toomey
2017-01-04 20:59 ` Kay Parker
2017-01-05 3:37 ` Greg 'groggy' Lehey [this message]
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=20170105033717.GD99823@eureka.lemis.com \
--to=grog@lemis.com \
/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).