I've hit a bit of a weird order of events (bug?) when copying a folder
that is part of the repository already, and using that as a starting
point for parallel future modifications. I understand why within that
folder (and sub folders) it might not show differences, after all
the .svn data matches, but it seems like the parent folder should be
able to say 'hey, there's a new folder here', or perhaps a bit further
and say 'hey, the sub folder svn data doesn't match the path I thought
it would have'.
Wanted to see if this is a misconception of mine. This is the only
confusing item I have hit so far with it.
Example:
Directory_A\
Directory_B\
File_A_B
If I copy File_A_B it can tell there is a new file. If I copy
Directory_B, paste it in Directory_A, and call it Directory_C.
Directory_A still retains checked and a commit shows now new files.
Directory_A\
Directory_B\
File_A_B
Directory_C\
File_A_B
Is there a reason the data related to Directory_A doesn't cause
Directory_C to be flagged? I understand a commit from either B or C
would update the repo's B, I keep feeling like I'm not understanding
why this is happening.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-05-15 21:13:45 CEST