problem with cvs

--MfFXiAuoTsnnDAfZ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Hi,

This is not texi2html related, but more cvs related. I have had a failure
when doing a cvs commit:

Checking in Tests/nodes_texinfo_res/texinfo.passfirst;
/cvs/texi2html/Tests/nodes_texinfo_res/texinfo.passfirst,v  <--  texinfo.passfir
st
new revision: 1.9; previous revision: 1.8
done
cvs commit: warning: unrecognized response `ndex fn' from cvs server
cvs commit: warning: unrecognized response `' from cvs server
cvs commit: warning: unrecognized response `' from cvs server
cvs commit: warning: unrecognized response `@node Concept Index' from cvs server
cvs commit: warning: unrecognized response `@unnumbered Concept Index' from cvs 
server
cvs commit: warning: unrecognized response `' from cvs server
cvs commit: warning: unrecognized response `@printindex cp' from cvs server
cvs commit: warning: unrecognized response `' from cvs server
cvs commit: warning: unrecognized response `' from cvs server
cvs commit: warning: unrecognized response `' from cvs server
Checking in Tests/nodes_texinfo_res/texinfo_283.html;
/cvs/texi2html/Tests/nodes_texinfo_res/texinfo_283.html,v  <--  texinfo_283.html
new revision: 1.4; previous revision: 1.3
done

and cvs stopped at the end of the commit for that directory with an error
message I haven't wrote down, but I remember it spoke about dying gasps.

Now the file that was commited was modified during that commit, some error
messages crept in. I attache a diff with the original file. It seems to me
that the error message is:
cvs [log aborted]: cannot get working directory: No such file or directory

I will re commit the original file.

Pat

--MfFXiAuoTsnnDAfZ
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: attachment; filename="commited_file.diff"
Content-Transfer-Encoding: 8bit

--- -	2003-08-05 13:34:42.392467000 +0200
+++ /home/dumas/tmp/file1.notag	2003-08-05 13:33:26.000000000 +0200
@@ -15223,7 +15223,7 @@
 @subsubheading Definition Commands
 
 Definition commands are @code{@@deffn}, @code{@@defun},
-@code{@@defmac}, and the like, and enable you to write descriptions in
+@code{@@defmac}, and the like, and enablecvs you to write descriptions in
 a uniform format.
 
 @itemize @bullet
@@ -15361,7 +15361,7 @@
 @subsubheading Invoking from a Shell
 
 You can invoke programs such as Emacs, GCC, and @code{gawk} from a
-shell.  The documentation for each program should contain a section that
+shell.  The docum entation for each program should contain a section that
 describes this.  Unfortunately, if the node names and titles for these
 sections are all different, they are difficult for users to find.
 
@@ -15519,7 +15519,7 @@
 
 Here is a numbered list.
 
-@@enumerate
+[@@enumerate
 @@item
 This is the first item.
 
@@ -15639,7 +15639,7 @@
 license is included in the section entitled ``GNU Free Documentation
 License.''
 
-(a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify
+(alog) The FSF's Back-Cover Text is: ``You have freedom to copy and modify
 this GNU Manual, like GNU software.  Copies published by the Free
 Software Foundation raise funds for GNU development.''
 @@end quotation
@@ -15766,7 +15766,7 @@
 pointers of the @code{@@node} line that begins the included file.  Also,
 you cannot use the regular commands to create a master menu for the
 whole file.  Either you must insert the menus and the `Next',
-`Previous', and `Up' pointers by hand, or you must use the GNU Emacs
+`Previous', and `Up' pointers by  aborted]hand, or you must use the GNU Emacs
 Texinfo mode command, @code{texinfo-multiple-files-update}, that is
 designed for @code{@@include} files.
 
@@ -15880,7 +15880,7 @@
 @cindex @code{@@include} file sample
 
 Here is an example of a complete outer Texinfo file with @code{@@include} files
-within it before running @code{texinfo-multiple-files-update}, which
+within it before running @c: ode{texinfo-multiple-files-update}, which
 would insert a main or master menu:
 
 @example
@@ -16007,7 +16007,7 @@
 printed on both sides of the paper.  Typically, you will use these
 formats, but you can specify your own format if you wish.
 
-In addition, you can specify whether chapters should begin on a new
+In addicannot get working directorytion, you can specify whether chapters should begin on a new
 page, or merely continue the same page as the previous chapter; and if
 chapters begin on new pages, you can specify whether they must be
 odd-numbered pages.
@@ -16101,7 +16101,7 @@
 
 @TeX{} does not begin to generate page headings for a standard Texinfo
 file until it reaches the @code{@@end titlepage} command.  Thus, the
-title and copyright pages are not numbered.  The @code{@@end
+title and copy: right pages are not numbered.  The @code{@@end
 titlepage} command causes @TeX{} to begin to generate page headings
 according to a standard format specified by the
 @code{@@setchapternewpage} command that precedes the
@@ -16317,7 +16317,7 @@
 may want to use the tools described in this appendix.
 
 @node Debugging with Info, Debugging with TeX, makeinfo Preferred, Catching Mistakes
-@section Catching Errors with Info Formatting
+@section Catching Errors with Info FoNo such file or directoryrmatting
 @cindex Catching errors with Info formatting
 @cindex Debugging with Info formatting
 
@@ -16434,7 +16434,8 @@
 For example, @TeX{} was run on a Texinfo file, part of which is shown
 here:
 
-@example
+@exam
+ple
 ---------- Buffer: texinfo.texi ----------
 name of the Texinfo file as an extension.  The
 @@samp@{??@} are `wildcards' that cause the shell to
@@ -17415,13 +17416,4 @@
 functions, and several variables.  To make the list easier to use, the
 commands are listed without their preceding @samp{@@}.
 
-@printindex fn
-
-
-@node Concept Index
-@unnumbered Concept Index
-
-@printindex cp
-
-
-
+@printi
\ Pas de fin de ligne à la fin du fichier.

--MfFXiAuoTsnnDAfZ--