"svn mv" after the fact??

It happens often to me that I do moves or renames and think about that just
before commit.

I know that it's not that difficult to remember. But it happens often that
some developer just do their work and it's left to me to check the changes
in. So sometimes I only discover with "svn st" that things have been moved or
renamed.

Trying to register this moving with svn results in a "unknown svn_node_kind" -
presumably because the source does no longer exist. --force didn't help,
either.

So I have to
1) move the files back
2) do a "svn mv"
which, as I know, could be automated away with a script, but nonetheless ...

How about using the special-case in which
a) source does no longer exist and
b) target does exist
just doing the bookkeeping without doing the move or showing an error??

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 1 12:25:55 2003