Re: Problems merging renamed file with contents changes

There is a "back story" to why rename is implemented as delete+copy
instead of as a single primitive. It's the scenario where someone
updates a tree in such a way as to receive only one side of a rename
event.

For example, Joe does

   $ svn rename foo/blah.c bar/blah.c

Then, Veronica does

   $ cd foo # (or bar)
   $ svn update

When Veronica updates, she should experience the delete (or copy) that
occurred in the tree she's updating, yet *not* experience the
corresponding other event, since that occurred in a place she's not
updating.

I'm not sure how this affects the discussion. Perhaps we just weren't
imaginative enough when we were implementing rename, and it's actually
possible to have atomic renames and also have Veronica's update work
correctly. I just wanted to explain the back story, and make sure
that people keep the scenario in mind when they're thinking about this
problem.

-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 12 07:11:48 2002