[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

rename problem

From: Andrew Gabriel <Andrew.Gabriel_at_clearswift.com>
Date: 2006-03-27 23:42:44 CEST

I think we may have found a problem in subversion, which leads to loss
of changes to a file when it is renamed under certain circumstances.
It was first reported to me by staff using the Eclipse client on
Windows XP, but I have reproduced it using the command line on Unix
too. Subversion is 1.3.0 (server Solaris x86, client Linux x86),
using svn:// access mode. The scenario to reproduce goes like this...

Assume person A and person B have a checked out workspace, and for
simplicity, we'll assume they checked out the same revision 1000
(although that's not a prerequisite). Person A edits a file and
commits it back creating revision 1001. Person B still has the older
revision in their workspace and renames this file. When person B
attempts to commit, Subversion correctly points out their workspace
is out of date. So person B updates their workspace which appears to
work fine, but actually hasn't changed the file contents. Person B
now commits their change creating revision 1002. The copy part
of the rename operation is shown as being copied from revision 1000,
thus losing the revision 1001 change.

Is this a known issue?

Andrew Gabriel
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Mar 27 23:38:42 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.