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

Code Loss!?

From: Irvine, Chuck R [EQ] <Chuck.R.Irvine_at_Embarq.com>
Date: 2007-04-10 19:12:35 CEST

I just read this in the SVN Book:

"...suppose that while working on your private branch, you rename
integer.c to whole.c. Effectively you've created a new file in your
branch that is a copy of the original file, and deleted the original
file. Meanwhile, back on trunk, Sally has committed some improvements to
integer.c. Now you decide to merge your branch to the trunk. ...The
merge operation has deleted the latest version of integer.c file (the
one containing Sally's latest changes), and blindly added your new
whole.c file - which is a duplicate of the older version of integer.c.
The net effect is that merging your "rename" to the branch has removed
Sally's recent changes from the latest revision!"

Coming from CVS, I was happy to have rename and move functionality, but
now I'm not so sure.

I consider pretty serious: there is a known, predictable situation that
will result in code loss. I'd have to consider this a "defect" and not a
"feature". Does anyone know if this is being worked on? Thanks


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 10 19:13:14 2007

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