Re: cvs.texinfo updates? add/remove

[Kevin R. Bulgrien]

> > 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.
> > 
> > My guess is that you need a patch like this one:
> > 
> > @@ -8248,6 +8248,7 @@ reference to @sc{cvs} commands, @pxref{I
> >  * Global options::              Options you give to the left of cvs_command
> >  * Common options::              Options you give to the right of 
> > cvs_command
> >  * Date input formats::             Acceptable formats for date 
> > specifications
> > +* add::                         Adding new files and directories
> >  * admin::                       Administration
> >  * annotate & rannotate::        What revision modified each line of a file?
> >  * checkout::                    Checkout sources for editing
> > @@ -8260,6 +8261,7 @@ reference to @sc{cvs} commands, @pxref{I
> >  * ls & rls::                    List files in the repository
> >  * rdiff::                       'patch' format diffs between releases
> >  * release::                     Indicate that a directory is no longer in 
> > use
> > +* remove::                      Removing files
> >  * server & pserver::            Act as a server for a client on 
> > stdin/stdout
> >  * sign::                        Attach new OpenPGP revision signature
> >  * tag & rtag::                  Mark project snapshot for later retrieval
> > 
> > but I have not looked closely to determine if that works in the flow of
> > both the manual and the man page.
> 
> What is the correct way for me to "test" the patch so that I can avoid wasting
> your time with one that does not work?  Make clean/all in the doc directory,
> or is there more to it than that?

Yes, that looks like the way to get the messages you showed me, and yes, I
missed that section... Adding entries like your example patch allow make all
to run with no errors.
 
Kevin R. Bulgrien
http://kbulgrien.home.att.net/