From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 26258 invoked from network); 14 Sep 2020 20:08:57 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 14 Sep 2020 20:08:57 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 7EA9C9CB06; Tue, 15 Sep 2020 06:08:55 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id D832F9CAE7; Tue, 15 Sep 2020 06:08:34 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="NbnGiNlw"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id D56B99CAE7; Tue, 15 Sep 2020 06:08:33 +1000 (AEST) Received: from mail-ej1-f54.google.com (mail-ej1-f54.google.com [209.85.218.54]) by minnie.tuhs.org (Postfix) with ESMTPS id 2405E9CAE6 for ; Tue, 15 Sep 2020 06:08:33 +1000 (AEST) Received: by mail-ej1-f54.google.com with SMTP id i26so1686966ejb.12 for ; Mon, 14 Sep 2020 13:08:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=WMrxUfx7TR98x6Uocsl7w0HYIeDUGhjGtpUvoo2Nsro=; b=NbnGiNlwE07kGYMbtxodUgHjhNe/Vt/qb27GViC7Bx9qV2e7ZUXWDFg0D+zZAULcJt /neUeB8lFG2pAlaecuCdbQS07DcywbEOS/5rA1izLppIMQGRpoRypGpeAl46zmq9tJSP xaeax2Y4Tv2fZdgKxUhBCB6tZzIJ6Ch/8nNvwb+z3yr6Rltx6tiaobvD5XDR0sdzSwUv nr4y3YYhxyKXvVTj4ehrn4ZfDtBG5bcvJJ6S+ffs0GqZD+0uzIDfUHHTu0fv5R4agoX5 5lIrdK9vB+6YEJsT82jeH0fKo0KdCPhOYBLad/Yz7tichUvEMop62S+DiU7v/xtXQ3zq UraA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=WMrxUfx7TR98x6Uocsl7w0HYIeDUGhjGtpUvoo2Nsro=; b=Yz550smn4DEFPCOhWjvW1j7Lb+t263gh7TWhExn0y9oDatsPnt2udEF5PVS06bdGaP 1KnLFvfLkaBfDQzScuRhABOMxYMkYs8sml3MSZcFU++I3nBJCeh9lI/ppigIPNPM0pjs yeN5agwQV7l6qxLUDooAVXyaCDBGOGignFRDrKjZ9XHUYfO69lSmH+v32rOBWhP2n8ie w3zBcOSL03bHZSdcP7JSq/ZGs4o9Grwk88Vt6Lz/Tq1ngii3CDS0aHq28wK4vTQsYfak T59/T/VMpGDd2dadIC/uHvA4iDWilMvxVJ9WMHiXaCeEvL0H6My5RETYjiXJKdYlm6c3 GG+w== X-Gm-Message-State: AOAM533q0vCSxZI5h4otlqClGqr3NSs0mk5doLvTnOA6q8l29IQgVjQG 6/46LWdNQdc+anx8XMdWrdJQy4KVFQrpbrI4WTk= X-Google-Smtp-Source: ABdhPJxI/vTjXK1fWutyiKBNi+FiZBSVn0NOhzGj8rD3xFSZAD6Fyrl2DviFxssPCrFYQS0/i5Cc3/c/8uKUX9uLxG0= X-Received: by 2002:a17:906:3748:: with SMTP id e8mr13031933ejc.71.1600114111661; Mon, 14 Sep 2020 13:08:31 -0700 (PDT) MIME-Version: 1.0 References: <5f5fc849.1c69fb81.8127c.ee16@mx.google.com> In-Reply-To: From: Henry Bent Date: Mon, 14 Sep 2020 16:08:21 -0400 Message-ID: To: Warner Losh Content-Type: multipart/alternative; boundary="00000000000039cc7e05af4b99d7" Subject: Re: [TUHS] revision history of troff -me macro set? X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: saint.snit@gmail.com, TUHS main list Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --00000000000039cc7e05af4b99d7 Content-Type: text/plain; charset="UTF-8" On Mon, 14 Sep 2020 at 16:04, Warner Losh 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 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 --00000000000039cc7e05af4b99d7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, 14 Sep 2020 at 16:04, Warner Losh <imp@bsdimp.com> wrote:
There should be copies in 4BSD = releases.=C2=A0

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=C2=A0

On Mon, Sep 14, 2020, 1:46 PM <saint.snit@gmail.co= m> 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.=C2=A0 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.=C2=A0 I posted this query on the troff email list,<= br> but no one there knew the answer, and one person suggested I ask here.)

Thanks for any pointers.

=
--00000000000039cc7e05af4b99d7--