From: Douglas McIlroy <email@example.com>
To: TUHS main list <firstname.lastname@example.org>
Subject: [TUHS] Bell Labs CSTRs
Date: Sat, 1 Jul 2023 14:03:37 -0400 [thread overview]
Message-ID: <CAKH6PiWrmz9RSwTgjLp_-jGfJsUgerA0OC6UQqrN7aR2qWwAMg@mail.gmail.com> (raw)
> once you've got M3 and M4, you've got a naming convention; I'd
> think it a safe bet that there was an M5 that was an internal
> experiment, and that M6 was simply the next in line
M6 came first, created by Andy Hall as a portability tool for Altran.
I always assumed the name echoed Ken Knowlton's L6 (BelL Labs low
level list language, with a superscript 6). I seem to recall that M6
was endowed with a very labored acronym.
next reply other threads:[~2023-07-01 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-01 18:03 Douglas McIlroy [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-25 17:44 arnold
2023-06-29 7:14 arnold
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).