From: Jon Steinhart <jon@fourwinds.com>
To: tuhs@tuhs.org
Subject: Re: [TUHS] Signal/noise
Date: Sun, 03 Feb 2019 22:20:31 -0800 [thread overview]
Message-ID: <201902040620.x146KVei010122@darkstar.fourwinds.com> (raw)
In-Reply-To: <1ACB2A2B-FE88-42E4-B08A-BDA6D074D902@bitblocks.com>
Bakul Shah writes:
> On Feb 3, 2019, at 6:37 PM, Larry McVoy <lm@mcvoy.com> wrote:
> >
> > And I must say you have done a great job of handling stuff going off
> > course. I don't mind a little wander, this list reminds me a lot of
> > Usenet around 1985 or so. Not a ton of people but most are pretty
> > darn interesting. So your policy of letting it wander a bit seems
> > just right to me, yeah the Jimmy Page guitar thing was way off track
> > but it wound down fairly quickly.
>
> I have said this before (or at least thought it!) but I, and I
> suspect some others, think of TUHS much like comp.unix.wizards
> of the old.
>
> Though Jimmy >PAGE< would certainly fit TUHS :-)
Yeah, I was really wanting the poster of George Goebels playing his two-headed VAX.
next prev parent reply other threads:[~2019-02-04 6:21 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 ` [TUHS] Signal/noise Warren Toomey
2019-02-04 2:37 ` 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 [this message]
[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=201902040620.x146KVei010122@darkstar.fourwinds.com \
--to=jon@fourwinds.com \
--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).