From: "Jeremy C. Reed" <reed@reedmedia.net>
To: saint.snit@gmail.com
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] revision history of troff -me macro set?
Date: Mon, 14 Sep 2020 16:41:16 -0500 (CDT) [thread overview]
Message-ID: <alpine.NEB.2.21.2009141632010.23559@t1.m.reedmedia.net> (raw)
In-Reply-To: <5f5fc849.1c69fb81.8127c.ee16@mx.google.com>
> Is there a repository of historical versions of Eric Allman's -me macro
> set for troff?
Also see
https://minnie.tuhs.org/cgi-bin/utree.pl?file=2BSD/doc/me
https://minnie.tuhs.org/cgi-bin/utree.pl?file=2BSD/bin/lib/me
(especially revisions and tmac.e)
https://minnie.tuhs.org/cgi-bin/utree.pl?file=2BSD/src/me
(again revisions and tmac.e)
And look at the SCCS "s.revisions" file
While it says "First Release: 11 Sept 1978" there is also a tmac.e
included and used by docs in 1BSD for exrefm.
next prev parent reply other threads:[~2020-09-14 22:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 19:33 saint.snit
2020-09-14 20:02 ` Warner Losh
2020-09-14 20:08 ` Henry Bent
2020-09-14 20:57 ` Eric Allman
2020-09-14 21:41 ` Jeremy C. Reed [this message]
2020-09-17 6:20 saint.snit
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=alpine.NEB.2.21.2009141632010.23559@t1.m.reedmedia.net \
--to=reed@reedmedia.net \
--cc=saint.snit@gmail.com \
--cc=tuhs@minnie.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).