From: Henry Bent <henry.r.bent@gmail.com>
To: Warner Losh <imp@bsdimp.com>
Cc: saint.snit@gmail.com, TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] revision history of troff -me macro set?
Date: Mon, 14 Sep 2020 16:08:21 -0400 [thread overview]
Message-ID: <CAEdTPBfgjBVMUMb96mke-eSJrjtwgkEE1VJfUXhRJ=zTVQ9GHA@mail.gmail.com> (raw)
In-Reply-To: <CANCZdfriL742xZs+ogH4iMfPKacSe7kQkE2eZOHRYkX9HVoGiQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]
On Mon, 14 Sep 2020 at 16:04, Warner Losh <imp@bsdimp.com> wrote:
> There should be copies in 4BSD releases.
>
> But it is also in the SCCS files as share/me/SCCS/s.tmac.orig_me and that
> has what looks like a complete history.
>
> Warner
>
> On Mon, Sep 14, 2020, 1:46 PM <saint.snit@gmail.com> wrote:
>
>> Hi,
>>
>> Is there a repository of historical versions of Eric Allman's -me macro
>> set for troff?
>>
>> (For some context: the macro set has been forked to operate with two
>> modern troff implementations: GNU groff and Heirloom troff. According
>> to the header blocks of the respective files, groff's -me macros are
>> forked from version 2.31 of Allman's, and Heirloom's from version 2.14.
>> For help in debugging -me problems in these troff implementations,
>> I'm trying to locate at least these versions of the -me package as they
>> existed before forking. I posted this query on the troff email list,
>> but no one there knew the answer, and one person suggested I ask here.)
>>
>> Thanks for any pointers.
>>
>
Here's a link:
https://svnweb.freebsd.org/csrg/share/me/tmac.orig_me?view=log
-Henry
[-- Attachment #2: Type: text/html, Size: 1999 bytes --]
next prev parent reply other threads:[~2020-09-14 20:08 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 [this message]
2020-09-14 20:57 ` Eric Allman
2020-09-14 21:41 ` Jeremy C. Reed
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='CAEdTPBfgjBVMUMb96mke-eSJrjtwgkEE1VJfUXhRJ=zTVQ9GHA@mail.gmail.com' \
--to=henry.r.bent@gmail.com \
--cc=imp@bsdimp.com \
--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).