The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Larry McVoy <lm@mcvoy.com>
To: Chet Ramey <chet.ramey@case.edu>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Proper use of TUHS (was Re: Typesetter C compiler)
Date: Fri, 3 Feb 2023 06:15:40 -0800	[thread overview]
Message-ID: <20230203141540.GS30555@mcvoy.com> (raw)
In-Reply-To: <73d0b98b-ae3f-428d-1b2e-feada7fc98a1@case.edu>

On Fri, Feb 03, 2023 at 09:11:35AM -0500, Chet Ramey wrote:
> On 2/2/23 8:44 PM, Dave Horsfall wrote:
> 
> >>So, the question becomes: what _is_ that forum, if such a thing exists
> >>at all?
> >
> >A new list?  Social media is for the birds; Usenet is dead, film at 11.
> 
> A new list, if it serves its purpose of providing interesting content, will
> eventually undergo the same thing. It's always going end up being some
> variant of Yogi Berra's famous "nobody goes there anymore, it's too
> crowded."

In my opinion, Warren has been threading the needle nicely.  He lets stuff
go into the weeds a bit but has a pretty good sense of when it is annoying
people that we all want to keep around.  He's very understated about it
all but he keeps this list pretty sane.

If you haven't joined COFF, maybe consider it, if that got big enough
then the other stuff could be done over there.

  reply	other threads:[~2023-02-03 14:15 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-02 19:02 [TUHS] Typesetter C compiler Noel Chiappa
2023-02-02 21:57 ` [TUHS] " Jonathan Gray
2023-02-03  0:43   ` Jonathan Gray
2023-02-02 22:36 ` [TUHS] Proper use of TUHS (was Re: Typesetter C compiler) Dan Cross
2023-02-02 22:41   ` [TUHS] " Larry McVoy
2023-02-02 22:47     ` Jim Capp
2023-02-03  1:44   ` Dave Horsfall
2023-02-03 13:17     ` Alan D. Salewski
2023-02-03 13:55       ` Larry McVoy
2023-02-06 20:02         ` Chris Hanson
2023-02-03 14:11     ` Chet Ramey
2023-02-03 14:15       ` Larry McVoy [this message]
2023-02-03 16:39         ` Dan Cross
2023-02-03 16:54           ` Larry McVoy
2023-02-03 17:08             ` Dan Cross
2023-02-03 17:11             ` Steve Nickolas
2023-02-03 17:26               ` [TUHS] move to COFF " Will Senn
2023-02-03 17:31                 ` [TUHS] " Will Senn
2023-02-03 17:45           ` [TUHS] " Bakul Shah
2023-02-05 10:42             ` steve jenkin
2023-02-04  8:03           ` [TUHS] A List for New Systems Influenced by History. (Was: Proper use of TUHS) Ralph Corderoy
2023-02-04 13:56             ` [TUHS] " Larry McVoy
2023-02-04 17:31               ` [TUHS] Re: A List for New Systems Influenced by History Angel M Alganza
2023-02-03  6:36   ` [TUHS] Re: Proper use of TUHS (was Re: Typesetter C compiler) Lars Brinkhoff
2023-02-04 22:38     ` Tomasz Rola

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=20230203141540.GS30555@mcvoy.com \
    --to=lm@mcvoy.com \
    --cc=chet.ramey@case.edu \
    --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).