[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Groff] [Heirloom] Request for testing a release candidate

From: Dorai Sitaram
Subject: Re: [Groff] [Heirloom] Request for testing a release candidate
Date: Thu, 18 Feb 2016 18:38:03 +0000 (UTC)

Hi Carsten:
[Sorry. didn't send to group on first try.]
This is somewhat related.  What is the canonical way to determine using generic 
troff commands that the troff being used is Heirloom troff, without regard to 
whether compatibility is off or on?  (I used to test the number register .g to 
rule out groff, but apparently that is not correct anymore.)
(This should ease testing with existing file bases.)

    On Thursday, February 18, 2016 4:32 AM, Carsten Kunze <address@hidden> 

 Werner LEMBERG <address@hidden> wrote:
> Ah, I wasn't aware that the project moved to github.  Please commit a
> last change to the CVS repository that explains that the project has
> moved, and that the CVS repository is now defunct!  Ditto for

That would indeed make sense.  Unfortunately only Gunnar has access to the 
SourceForge CVS and web page.  There is only read access to the CVS possible 
for others.

The last change on the CVS repository had been on June 19, 2011.  Gunnar has 
silently abondoned the project without prior notice and is not reachable since 

At the time when severe bugs had been found I tried to contact Gunnar but I got 
no answer.  Later I also asked for access to the CVS or at least be able to 
place a notice at the web page, but again he didn't answer.  The maintainer of 
the Mac OS X port (Stefan Tramm) finally did suggest to move the project to 
GitHub.  There it is continued since August 2014.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]