From: Dan Cross <crossd@gmail.com>
To: segaloco <segaloco@protonmail.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Bell Labs CSTRs
Date: Sat, 1 Jul 2023 14:42:07 -0400 [thread overview]
Message-ID: <CAEoi9W4yxYN4wLE9HJLeGtELabyCG1pLRSTW7kXCboYCEasZdQ@mail.gmail.com> (raw)
In-Reply-To: <9Lm966Be4OkPcrr0D_46OoESAtnWwi7DYjtwvIwKJsB81QIwMmSKIzz5F_JyalhwOXAMP2vdJQwpKuq4jGJryXOcKBAQY7S-r24_Aagb8ss=@protonmail.com>
On Sat, Jul 1, 2023 at 2:03 PM segaloco <segaloco@protonmail.com> wrote:
> > Anyway, 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 and was
> > interesting enough to be documented in a tech report.
>
> Only problem there is m6 predates m3 and m4. Th m6(I) page first appears in V2 and there is a published reference from 1972. Software Tools, from which m3 derives, was 1976, and m4 was then introduced in V7 (which is also the first research version since V2 without m6 somewhere in the manual.)
>
> Here's a rough history of the m6 manpage: https://gitlab.com/segaloco/mandiff/-/commits/v6/man6/m6.6
Oops. Very well, then: stab my stab with a fork, for it is dead.
- Dan C.
next prev parent reply other threads:[~2023-07-01 18:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 7:14 [TUHS] " arnold
2023-06-29 7:36 ` [TUHS] " Noel Hunt
2023-06-29 14:40 ` Clem Cole
2023-06-29 15:04 ` Will Senn
2023-07-01 17:28 ` Dan Cross
2023-07-01 18:03 ` segaloco via TUHS
2023-07-01 18:42 ` Dan Cross [this message]
2023-06-29 15:14 ` Will Senn
2023-08-26 17:02 Nelson H. F. Beebe
2023-08-27 3:13 ` Jonathan Gray
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=CAEoi9W4yxYN4wLE9HJLeGtELabyCG1pLRSTW7kXCboYCEasZdQ@mail.gmail.com \
--to=crossd@gmail.com \
--cc=segaloco@protonmail.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).