tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Guy Harris <guy@alum.mit.edu>
To: tech@mandoc.bsd.lv
Subject: Re: Should .At 32v rather be [AT&T] UNIX/32V rather than Version 32 AT&T UNIX?
Date: Wed, 18 Aug 2021 23:34:16 -0700	[thread overview]
Message-ID: <8F26DC01-86AD-420E-B6E2-658C53B0F5C7@alum.mit.edu> (raw)
In-Reply-To: <20210818184652.gp3apndkyoa2m3kc@tarta.nabijaczleweli.xyz>

On Aug 18, 2021, at 11:46 AM, наб <nabijaczleweli@nabijaczleweli.xyz> wrote:

> My reasoning being that 32V is a direct port of V7 to the VAX
> with single-digit and non-formative new utilities (tsort, ..?);
> bundling it in with V[1234567] is, at its best, disingenuous,
> and, at worst, just plainly wrong.

In what way does calling it "Version 32V AT&T UNIX" bundle it in with V[1-7]?

(BTW, tsort was in V7, but I digress.)

However:

> The designations of early unices originate in their manuals;
> how does 32V stack up here?

Yes, Bell Labs appeared to call it UNIX/32V, not Version 32V AT&T UNIX.

However however, if the goal was to be compatible with current versions of -mdoc, then calling it Version 32V AT&T UNIX achieves that goal.  That appears to date back at least as far as 4.4-Lite-2, from a quick "egrep -i 32v" in Lite-2's /usr/src/share/tmac directory.

Presumably, from the Debian bug you filed, your goal is to get all implementations of -mdoc changed, not just the mdoc implementation.

(Note, BTW, that calling V7 "Version 7 AT&T UNIX" also dates back to Lite-2's -mdoc (if not earlier); I'm not sure whether the *operating system* had an official name, or whether it was just the UNIX Programmer's Manual that came with it being the Seventh Edition of the manual.)--
 To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv


  reply	other threads:[~2021-08-19  6:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-18 18:46 наб
2021-08-19  6:34 ` Guy Harris [this message]
2021-08-19 11:54   ` наб
2021-08-19 15:13     ` Ingo Schwarze
2021-09-01 16:53       ` наб
2021-09-02 12:40         ` Ingo Schwarze

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=8F26DC01-86AD-420E-B6E2-658C53B0F5C7@alum.mit.edu \
    --to=guy@alum.mit.edu \
    --cc=tech@mandoc.bsd.lv \
    /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).