Re: weird behavior with simultaneous edit and move

--Saulius Grazulis <grazulis@akl.lt> wrote:

> On Sunday 04 December 2005 07:03, Kent Tong wrote:
>> Would anyone confirm the following weird behavior with simultaneous
>> edit and move?
>>   client 1: renames F1 to F2.
>>   client 2: edits F1.
>>   client 1: commits.
>>   client 2: synchronizes. F2 will appear as a new file (incoming
>> change). F1 will be marked as in conflict with the content of F2.
>>   client 2: marks F1 as resolved. Updates. Then F1 will become an
>> unversioned file! It means he will have both F1 and F2! And F2
>> doesn't contain the changes he made.
>
> To my taste, this looks as completely expected and normal behavior. Since
> user 1 renamed F1, thus effectively removing it from version control,
> any file named F1 from that point on becomes unversioned.

Somewhere along the line, client 1 should communicate with his team and let
them all know that he has renamed the file. This is especially true if the
file is one that more than one person may be working on. A version control
system cannot replace effective communications.

-- 
Bruce Webber
brucewebber@fastmail.us
http://brucewebber.us
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org