====================================
Q: What's the meaning of the message:

unrecognizable line in ./CVS/Entries.Log, try "cvs commit"
------------------------------------
A: From CVS documentation:

`Entries.Log'
     This file does not record any information beyond that in
     `Entries', but it does provide a way to update the information
     without having to rewrite the entire `Entries' file, including the
     ability to preserve the information even if the program writing
     `Entries' and `Entries.Log' abruptly aborts.

cvsu, as of version 0.1.2, supports only two types of lines in Entries.Log,
namely directories scheduled for adding or removing.

Those entries are sometimes left in Entries.Log when "cvs update -d" is
run.

However, if there are other entries in Entries.Log, it may indicate that
the state of the working directory is inconsistent.

In this case, it is safe to run "cvs commit", even if you are offline
or don't have write access to the repository. If this command spawns an
editor (vi by default), you should exit and abort commit.

To exit from vi, press consequently "Escape" ":" "q" "!" "Enter"

CVS maintainers have been asked to introduce a better command to apply
pending changes in Entries.Log to Entries
====================================
Q: cvsu properly handles contents of .cvsignore but displays the .cvsignore
file with question mark as an unknown file. IMHO it should not do it this
way.
------------------------------------
A: This is exactly what "cvs up" does. I tried to emulated the behaviour of
CVS as long as it was practical. If you want to get rid of the question
mark you should either put .cvsignore to .cvsignore or add .cvsignore to
the repository. This applies both to cvsu and cvs.
====================================