From: Angel M Alganza <ama@ugr.es>
To: tuhs@tuhs.org
Subject: [TUHS] Re: A List for New Systems Influenced by History.
Date: Sat, 04 Feb 2023 18:31:01 +0100 [thread overview]
Message-ID: <ab2f8c7d02239b2a7153d4ace6a5d636@ugr.es> (raw)
In-Reply-To: <20230204135603.GA27395@mcvoy.com>
On 2023-02-04 14:56, Larry McVoy wrote:
> We need as much mass as we can get from tuhs and then we
> advertise on stackoverflow and hacker news and ?
On nostr, maybe? There are tons of technical people there celebrating
how cool it's having the same feelings they had 25-30 years ago when
they discovered the Internet first, when it was still full of hope of
being decentralized and free. I think tuhs and, probably even more, coff
might be the perfect fit for them.
Cheers,
Ángel
next prev parent reply other threads:[~2023-02-04 17:31 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 ` Angel M Alganza [this message]
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=ab2f8c7d02239b2a7153d4ace6a5d636@ugr.es \
--to=ama@ugr.es \
--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).