Re: Local modifications to a "moved" path.

On Fri, 2004-08-06 at 05:35, Nick Patavalis wrote:

> The question is, since svn knows about the ancestry of f2.txt,
> couldn't (and shouldn't) it handle the operation in a completely
> transparent manner? That is:
>
> Use 1:
> svn update
> ... Moving f1.txt to f2.txt (with local mods) ...
> ... Merging f2.txt (nothing to merge) ...
>
> Are there conseptual "gotchas" in such a behavior, or is it not done
> merely due to implementation complexity?

This is a well-known problem. Subversion doesn't have "real moves" --
only copies and deletes. The server doesn't tell the client to "move"
anything, it just sends an "add" of a copied file, and a "delete" of the
old file. It lacks the vocabulary to express a "move" concept to the
client.

We plan to fix that someday (like, in the next year), but for now
there's no real workaround.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 6 15:12:06 2004