From: Warren Toomey <wkt@tuhs.org>
To: tuhs@tuhs.org
Subject: Re: [TUHS] Signal/noise
Date: Mon, 4 Feb 2019 12:23:32 +1000 [thread overview]
Message-ID: <20190204022332.GA14788@minnie.tuhs.org> (raw)
In-Reply-To: <CAPWNY8Wx87Qx+gP+bm-YskuGbvu1pXoh2=rWafA50u8zWxSY-w@mail.gmail.com>
> So I don't know what counts as 'signal' on this list versus 'noise',
> but I'd much rather read a million posts about OSI, CLNP and other
> networks – a history lesson and information that's been getting scarce
> in general – than kill/mute yet another thread full of generic "boo M$
> Windoze" drivel that I can already find on Reddit.
Warren's protocol for off-topic material: let it slide for a day or two,
then politely ask people to move it to the COFF list when it doesn't
veer back to the Unix direction :-)
Cheers, Warren
next prev parent reply other threads:[~2019-02-04 2:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-03 15:02 [TUHS] OSI stack (Was: Posters) Noel Chiappa
2019-02-03 16:51 ` Grant Taylor via TUHS
2019-02-03 23:33 ` [TUHS] Signal/noise (Was: OSI stack (Was: Posters)) Mantas Mikulėnas
2019-02-04 0:10 ` Arthur Krewat
2019-02-04 0:54 ` Grant Taylor via TUHS
2019-02-04 2:23 ` Warren Toomey [this message]
2019-02-04 2:37 ` [TUHS] Signal/noise Larry McVoy
2019-02-04 2:57 ` Bakul Shah
2019-02-04 3:26 ` Warner Losh
2019-02-04 3:26 ` Dan Cross
2019-02-04 4:55 ` Dave Horsfall
2019-02-04 6:20 ` Jon Steinhart
[not found] ` <CANCZdfq5PM9jFEi9=geC+CTnveXs5CprN7b+ku+s+FYzw1yQBw@mail.gmail.com>
2019-02-06 17:16 ` [TUHS] OSI stack (Was: Posters) Warner Losh
2019-02-06 17:23 ` Larry McVoy
2019-02-06 23:37 ` George Michaelson
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=20190204022332.GA14788@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).