Re: mkman.pl patch

[Kevin R. Bulgrien]

> This will fix it.  Basically, the "see node" is only used for @pxref{} and
> @xref{}.  Not beautiful, but it does work for cvs.1.  I did make
> maintainer-clean to remove the old mkman script, did a ./configure,
> and it produced a cvs.1 with:
> 
>        -f
> 
>          Note that this is not the standard  behavior  of  the  -f  option  as
>          defined in `Common options' in the CVS manual.

Ah, and it fixes other notes too, but does introduce a few other anomalies
elsewhere.  I'll review and patch them up in cvs.texinfo too.  A few @ref{}
need to be changed to @xref{}. 

For example of how this patch buggers up some of the man page content:

@@ -499,7 +499,7 @@
 environment variable (see node `Environment variables\(aq in the CVS manual) an
d the \fBsign\fR and
 \fBno-sign\fR method options (see node `The connection method\(aq in the CVS ma
nual).
 .SP
-\fBWARNING: see node `OpenPGP Signed Commits\(aq in the CVS manual for more on
using OpenPGP
+\fBWARNING: `OpenPGP Signed Commits\(aq in the CVS manual for more on using Ope
nPGP
 signatures securely.\fR
 .SP
 .IP "" 0
@@ -529,7 +529,7 @@
 This template should send the generated signature to its standard output.
 Overrides the \fBsign-template\fR method option and defaults to something like
 \fB/usr/bin/gpg --detach-sign --output - %M %@ %s\fR.
-\fBWARNING: see node `OpenPGP Signed Commits\(aq in the CVS manual for more on
using OpenPGP
+\fBWARNING: `OpenPGP Signed Commits\(aq in the CVS manual for more on using Ope
nPGP
 signatures securely.\fR
 .SP

--
Kevin R. Bulgrien
http://kbulgrien.home.att.net/