You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "BRUGGEMAN Jens (JBRG)" <Je...@seco-m.be> on 2004/10/25 13:14:24 UTC

Problem found in latest subversion

Hi,
 
I have found a pretty important bug in the latest subversion 1.1.0.
 
Consider the following situation:
You have two folders in the main repository being 'application1', and
'application2'.
User 'A' modifies the file 'application.cpp' en decides to move it to folder
'application2'.  SVN move: delete/add action and he succesfully commits.
User 'B' in mean-time changes his local copy of file 'application.cpp' in
the folder 'application1' and decides to do a SVN update.
Because of the update the file 'application.cpp', which has local
modifications, is deleted and is added in the 'application2' directory.
 
How can I solve this situation correctly so user 'B' does not loose his
local modifications?
 
Best regards,
Jens