Re: Timestamp race avoidance in do_update()

[Larry Jones]

Brad Chisholm writes:
> 
> Just to make sure I understand, CVS is sleeping to ensure that any post-CVS
> process which might modify the file must also change the timestamp.  This
> is necessary, because the CVS client relies on the timestamp to determine
> whether a file has been modified.  (i.e. if the current timestamp of the
> file matches the timestamp stored in the Entries file, then the client
> will consider the file unchanged, even if the contents have actually changed).

Exactly.  As I said in the thread you quoted, you should send all of the
file information first and then a single update command, not a separate
update command for each file.  Also, the current development version no
longer sleeps when in server mode; it is up to the client to do it
instead.

-Larry Jones

Monopoly is more fun when you make your own Chance cards. -- Calvin