The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Tomasz Rola <rtomek@ceti.pl>
To: TUHS <tuhs@tuhs.org>
Cc: coff@tuhs.org
Subject: [TUHS] Re: Proper use of TUHS (was Re: Typesetter C compiler)
Date: Sat, 4 Feb 2023 23:38:26 +0100	[thread overview]
Message-ID: <Y97eYk5rKUS68+Mc@tau1.ceti.pl> (raw)
In-Reply-To: <7wv8kj6yrx.fsf@junk.nocrew.org>

On Fri, Feb 03, 2023 at 06:36:34AM +0000, Lars Brinkhoff wrote:
> Dan Cross wrote:
> > So, the question becomes: what _is_ that forum, if such a thing
> > exists at all?
> 
> Some options:
> 
> - Cctalk email list.

(cc-ed to coff, of coffse...)

I use to hang out on IBM-MAIN mailing list, too. While they are,
mostly, dealing with modern mainframes and current problems, they also
occasionally mention old story or two. Actually, since mainframe is
such a living fossil thing, the whole talk sometimes feels as if it
was about something upgraded continuously from the 1960-ties. Most of
it is uncomprehensible to me (never had proper mainframe training, or
unproper one, and they deal with stuff in unique way, have their own
acronyms for things, there are some intro books but there is not
enough time*energy), but also a bit educating - a bit today, a bit
next week etc.

> - ClassicCMP Discord.
> - Retrocomputingforum.com.
> - Various Facebook groups.

Web stuff, requiring Javascript to work, ugh, ugh-oh. Mostly, it boils
down to the fact that one cannot easily curl the text from those other
places (AFAICT). So it is hard to awk this text into mbox format and
read it comfortably.

-- 
Regards,
Tomasz Rola

--
** A C programmer asked whether computer had Buddha's nature.      **
** As the answer, master did "rm -rif" on the programmer's home    **
** directory. And then the C programmer became enlightened...      **
**                                                                 **
** Tomasz Rola          mailto:tomasz_rola@bigfoot.com             **

      reply	other threads:[~2023-02-04 22:39 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
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 [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=Y97eYk5rKUS68+Mc@tau1.ceti.pl \
    --to=rtomek@ceti.pl \
    --cc=coff@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).