Tree conflict detection bug/limitation

This may be known already. I recall that we knew there were scenarios
involving folders where TC detection has not been added yet.

The attached script shows a pretty trivial merge example where it does
not detect a TC and it seems like we should. Basically, in a branch a
file is edited and committed. In trunk, the parent folder is renamed
and committed. Now trunk is merged to the branch. No conflict is
raised, so the changes to the file on the branch would not be flagged
as needing to go into the renamed file. I think at one point we might
have talked about "replaying" the rename on the branch so that the
content was preserved, but that does not seem to be happening either.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1334518