bug-cvs
[Top][All Lists]
Advanced

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

Re: cvs.texinfo updates? add/remove (newer patch)


From: Kevin R. Bulgrien
Subject: Re: cvs.texinfo updates? add/remove (newer patch)
Date: Sun, 13 Aug 2006 01:04:58 -0500
User-agent: KMail/1.8.2

> Hi Kevin,
> 
> makeinfo 4.8 does not like your patch.
> 
> % make cvs.info
> cvs.texinfo:11721: `remove' has no Up field (perhaps incorrect sectioning?).
> cvs.texinfo:9023: `add' has no Up field (perhaps incorrect sectioning?).
> makeinfo: Removing output file `cvs.info' due to errors; use --force to 
> preserve.
> %
> 
> So, you still have a bit of work to do before your patch may be used.

This patch supercedes the patch previously submitted, and may also be
freely distributed.

I  have incorporated Mark's suggestions.  make appears to build without
errors,  but I am still not quite sure how to properly make the workspace
clean so that make does its job.  make clean does not clean up cvs.1.
make maintainer-clean does, but also forces me to re-run ./configure.
Nonetheless, I believe I have corrected the problems that existed with
the other patch.

Also, I note an oddity in the man page that pre-dates my edits.  Various
command options carry this note:

         Note that this is not the standard  behavior  of  the  -f  option  as
         defined in see node `Common options' in the CVS manual.

The phrase "defined in see node" is awkward.  The textinfo manual says
that @ref{} does not generate the word "see" in printed documentation,
but apparently this does not include the info/man page documentation.
The source that generates this is:

        @table @code
        @item -f
        Note that this is not the standard behavior of
        the @samp{-f} option as defined in @ref{Common options}.

I do not know how to correct this, but, again, this is present in various
other locations in the man page.

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

Attachment: cvs.texinfo.krb.patch
Description: Text Data


reply via email to

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