From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Documents for UNIX Collections
Date: Thu, 11 Aug 2022 21:06:53 -0500 [thread overview]
Message-ID: <20220812020653.ltfxtvi5earzlbmk@illithid> (raw)
In-Reply-To: <zVLkYOXDMULs8ROpKVz-7jbOZXFe5gM0gtnpJhl8hw1g8N737Rts54AWyMzwIAmVFSoHP9mKiIltZkheQ-caace_QQEBe07gyCOccYuRl9g=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 825 bytes --]
At 2022-08-12T01:33:12+0000, segaloco via TUHS wrote:
> - Either the original EQN paper is dropped or relevant bits mashed
> together with the user's guide
V7 Unix shipped sources for both[1] but all typeset versions of the Unix
Programmer's Manual I've seen (both scanned and HRW's physical copies)
omit the white paper. Having recently undertaken to re-set these with
groff,[2] I surmise that this is because there was already much overlap
in content. What remained in the white paper was largely the de rigueur
journalese about why this contribution was significant and
scientifically noteworthy. It may have been felt that paid licensees
already perceived such value.
Regards,
Branden
[1] https://minnie.tuhs.org/cgi-bin/utree.pl?file=V7/usr/doc/eqn
[2] https://minnie.tuhs.org/pipermail/tuhs/2022-July/026090.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-08-12 2:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 1:33 segaloco via TUHS
2022-08-12 2:06 ` G. Branden Robinson [this message]
2022-08-12 6:41 ` arnold
-- strict thread matches above, loose matches on Subject: below --
2022-08-12 11:01 Paul Ruizendaal via TUHS
2022-08-12 11:15 ` arnold
2022-08-12 11:41 ` Jonathan Gray
2022-08-12 16:06 ` Warner Losh
2022-08-12 16:37 ` Warner Losh
2022-08-13 19:51 ` Paul Ruizendaal via TUHS
2022-08-08 23:52 segaloco via TUHS
2022-08-09 0:37 ` Al Kossow
2022-08-09 7:00 ` segaloco via TUHS
2022-08-09 12:49 ` Al Kossow
2022-08-09 15:14 ` segaloco via TUHS
2022-08-09 17:16 ` Warner Losh
2022-08-09 17:22 ` Will Senn
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=20220812020653.ltfxtvi5earzlbmk@illithid \
--to=g.branden.robinson@gmail.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).