Re: Why does cvs wait to the next second?

[Urs Thuermann]

Paul Sander <address@hidden> writes:

> The specific reason for this is because CVS assumes that it was the
> last to modify a file if its mod time matches the one recorded in
> its Entries file.  If it's quickly modified by something else, then
> CVS may still think it's up to date and both "cvs update" and "cvs
> commit" will produce incorrect results.
> 
> There has been much discussion on this topic, and you can see
> discussion of the rationale in the info-cvs archives.

OK, I've looked up the topic in the archives.  I assume it has already
been suggested to change the "Entries" file format to use a hash
instead of a time stamp.  But I haven't seen this in the info-cvs
archive.  So wouldn't this be an option?  Otherwise, I'd like a
command line option to disable the sleep, probably with a BIG warning
that it should only be used if you know what you do.

I have a script that calls cvs checkout hundreds to thousands of times
and that causes the script to run for half an hour or so instead of a
few seconds.  The info-cvs archive also suggests using RCS tools
instead of CVS.  Is it guaranteed that the CVS repository files will
always have RCS format and RCS tools will work on them?


urs