Re: serious commit problem

[Larry Jones]

Nils9 writes:
> 
> Checkout a branch, change one file, commit it back, then right after that,
> checkout next branch (contains the same file), quickly change it too (the same
> changes as in first branch) and commit back, and when you checkout the first
> branch again, the file changes are gone in this branch! The file changes both
> times were performed by overwriting the checked-out file with new version,
> and commited back.

Are you sure the commits are actually happening?  CVS assumes that a
file is unchanged if it's timestamp hasn't changed -- it you make
changes too quickly, it may be that CVS misses them and the commit
doesn't actually do anything.  CVS has a built-in sleep which should
prevent that from happening, but it doesn't quite work on Windows
because the Windows filesystem timestamps have a two second granularity
rather than the one second that CVS assumes.

-Larry Jones

It's going to be a long year. -- Calvin