2009-07-28 09:52 AEST by Arthur Barrett - We should find a 'better' solution to the one second resolution for entries/update/commit issue.

Commit relies on 'changed' files having a 'different' date/time to the checked out file.  However in a 
'script' it is possible to checkout a file, change it and then commit it all within a second.  

To 'work around' this issue the client currently waits until 'the next second' before returning control to 
the calling process when it processes an update/checkin/commit (indirectly because of the update for -
kkv).

For many uses this unnecessarily limits the performance of the product, and there must be some 'low 
cost' better solution - or at least an improvement, eg:
- global --nowait option
- update -F / commit -F forces files to be sent to the server regardless of date/time (not the same as 
'commit -f' which forces the server to treat the file as changed even if there are no differences).  ie: 'cvs 
update -F hello.txt' is the same as 'touch hello.txt; cvs --nowait update hello.txt'.  Programs like the 
SCC plugin could use 'cvs update -F' and 'cvs commit -F' for SCC control files like project.vsssc which 
visual studio may change at sub-second speed.