From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Stuff Received <stuff@riddermarkfarm.ca>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Trying to date "A Supplemental Document For Awk"
Date: Thu, 29 Jun 2023 08:45:50 -0500 [thread overview]
Message-ID: <20230629134550.mpffmezmm3xj2hrp@illithid> (raw)
In-Reply-To: <237fe42c-7803-33cc-68c3-c9a05966b95a@riddermarkfarm.ca>
[-- Attachment #1: Type: text/plain, Size: 545 bytes --]
At 2023-06-28T21:59:24-0400, Stuff Received wrote:
> and why was the compilation line never placed in a comment in the
> file?
Having done some work with historical *roff documents, my conjecture is
that the single source of truth was usually to be found in a Makefile.
Unfortunately, *roff documents have not reliably been distributed along
with the scripts directing control of their compilation and
installation. If you insist upon that, you start sounding like one of
those street-corner preaching copyleft people... ;-)
Regards,
Branden
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-06-29 13:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 6:26 [TUHS] " Aharon Robbins
2023-06-28 6:45 ` [TUHS] " arnold
2023-06-28 17:48 ` Adam Sampson
2023-06-28 18:03 ` KenUnix
2023-06-28 18:38 ` Clem Cole
2023-06-28 23:47 ` Greg 'groggy' Lehey
2023-06-29 1:59 ` Stuff Received
2023-06-29 6:27 ` segaloco via TUHS
2023-06-29 6:41 ` Andrew Hume
2023-06-29 6:45 ` Noel Hunt
2023-06-29 6:48 ` Andrew Hume
2023-06-29 6:50 ` arnold
2023-06-29 6:44 ` Noel Hunt
2023-06-29 14:02 ` G. Branden Robinson
2023-06-29 13:45 ` G. Branden Robinson [this message]
2023-06-29 13:34 ` G. Branden Robinson
2023-06-29 13:47 ` Rich Salz
2023-06-29 19:03 ` Steffen Nurpmeso
2023-06-29 1:04 ` Bakul Shah
2023-06-29 0:26 ` Jeremy C. Reed
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=20230629134550.mpffmezmm3xj2hrp@illithid \
--to=g.branden.robinson@gmail.com \
--cc=stuff@riddermarkfarm.ca \
--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).