Matt Gregory wrote:
>
> I've been managing our CVS use for about 3 years now and up until
> today I've been able to figure out an explanation for every weird CVS
> behavior. Here's what's happening:
>
> Developer A updates file x and gets version 1.200. However, changes
> are missing that exist in version 1.196. Developer B also updates
> file x and gets version 1.200, but has the changes from 1.196.
> Developer B is confused, so B adds a comment to file x and commits it
Hmm another one... I've been seeing dropping of updates for a while, but
it happens
rarely & I attributed it to errors in the diff algorythm. It seems that
sometimes
'cvs update' doesn't change the on-disk file, but *does* change the CVS
directory, which
causes a revision to be effectively erased on the next commit.
It might be that there's a problem when the clocks of the machines
aren't in sync (most of the time
this has happened it has involved a laptop which doesn't automatically
keep in sync like the
desktops do). I have watched it happen in front of me with a desktop,
though. I committed a bugfix,
went to the other machine to update, it said it had done the update, but
the bugfix did not propogate. I had
to manually delete the file and re-update to cause the new revision to
appear.
Tony
--
The only secure computer is one that's unplugged, locked in a safe,
and buried 20 feet under the ground in a secret location... and i'm
not even too sure about that one"--Dennis Huges, FBI.
[EMAIL PROTECTED]
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
