Re: avoid overwriting new files in the Repository during commit

On Dec 7, 2004, at 11:06 PM, Clemens Schwaighofer wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> I have just a small question.
>
> I have User A who works on file.pl and User B who does the same. User A
> changes something and commits, User B does the same right afterwards,
> without updateing his local copy.
>
> Subversion says nothing and just overwrites the file on the server.

That's not true at all! If so, it would completely violate the entire
concurrent "copy, modify, merge" model used by both CVS and Subversion.

What happens is: User B tries to commit, and gets an error message
saying that the commit failed because his copy of file.pl is "out of
date". User B is then forced to update and merge changes before
retrying the commit.

What makes you think otherwise?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 8 07:32:29 2004