Re: [TSVN] detecting a shell copied/moved subtree

SteveKing wrote:
> On 6/21/05, Hiroharu Tamaru <tamaru@myn.rcast.u-tokyo.ac.jp> wrote:
>> Hi. Sorry to bother you again.
>>
>> What if the 'mv' was a 'cp -r' ?
>>
> [snip]
>>
>> Is there a way to notice this mistake as in the mv case?
>
> Yes. It won't show up as 'added' with the new name/location.

What happens if you copy a WC folder from project B into project A by
mistake? It's the sort of mistake you can make in explorer if you miss
with the mouse, and then forget to sort out properly.

If you look in project A, project B is sitting there looking exactly
like one of project A's sub-folders, and if project A already has 30
subfolders, you might not notice one extra. The overlays don't show
anything, check for modifications doesn't show anything. So unless you
do some very careful checking you may not notice this for weeks.

In fact it is a perfectly legitimate nested working copy, for which we
include applications in our manual, so we are not doing anything wrong.
It's just that the CLI flags it up as not being part of the main
project, and we don't.

I think we are wrong here. We can show all versioned items, we can show
all external items and we can show all unversioned items, if you check
the right checkboxes. But nested WCs seem not to exist - we don't show
them at all.

Can we include some reference to these nested WCs in 'check for
modifications'? Maybe just list the folder status as 'Nested WC' without
recursing into it.

Simon

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org