[TSVN] detecting a shell copied/moved subtree

Hello,

I'm not sure how I call the issue, but for the moment, I'll
call it deteing a shell copied/moved subtree.
Could you please take a look at the following transaction:

{1}> svn co file:///path/to/the/repository work
A work/a
A work/a/file
Checked out revision 1.
{2}> cd work
{3}> svn st -v
                1 1 tamaru .
                1 1 tamaru a
                1 1 tamaru a/file
{4}> mv a x
{5}> svn st -v
? x
                1 1 tamaru .
! ? ? ? a
{6}> svn up
A a
A a/file
Updated to revision 1.
{7}> svn st -v
? x
                1 1 tamaru .
                1 1 tamaru a
                1 1 tamaru a/file

In step 4, I mistakingly renamed the directory a/ to x/
using a shell command and not the subversion way. But then,
using status command on the command-line client, it always
tells me that x/ is a result of such a failure, even though
there still is a .svn/ directory inside x/ .

Is there a way in TortoiseSVN to detect this in a similar way?

With TortoiseSVN, x/ even has a green checkmark overlay (I
understand why, so don't tell me :-p ), so it is diffcult to
notice it in the first place.

Running "Check for Modifications" will not show x/ as
non-versioned (as opposed to the case for the status command
in command-line client).

Yes, I noticed that if I check on "Show unmodified file" in
the status dialogue box, directory x/ will still not show
up. So, in principle, by comparing this status dialogue
with the acutual working copy, I can spot out that indeed
something has happened to x/ ; but that is impractical if it
is a directory deep inside some hierarchy of 1000+
directories and files.

Is it possible to detect such a case in TortoiseSVN?

I'm using 1.2.0, but I beleive it was so on 1.1.x as well.

Thank you.

-- 
Hiroharu Tamaru.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org