Re: Explorer Copy Issues

> No, because the nested working copy is not related in any way to its
> parent folder (in your case it happens to be so, but that is not the
> general case), so marking the parent as modified would be misleading.

I think this results in a lot of confusion for TortoiseSVN users (and
perhaps SVN in general). Every time a user copies and pastes without
using svn related tools, this becomes an issue. As a software feature
I see great value in this, and I do not think I would be completely
alone in that view.

Anyone looking to sync a network drive, or a laptop that has been out
of the network for some time faces these issues. There is nothing
about SVN that requires that users of the file system have SVN tools
installed, and this just seems like a rough edge that could easily
have caps placed on it. My $0.02 though...

Do you find yourself having sub folders that are duplicates or point
to different places in the repository(s), while being also under a
folder that is in a repository a lot? Perhaps I was wrong in thinking
that my situation would be more common.

> If you have people editing files and folders in a version controlled
> area without even knowing that it is version-controlled, that seems
> inherently error-prone to me.

Grin, it is. But the Tortoise software should be able to warn users.
Allowing Nested folders to optional impact icons and warnings before a
commit would address this.

Please don't take this as a bitter rant, just something I noticed and
thought was worth addressing. I'm really happy with tortoiseSVN
overall.

--
Matt (MPCM)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org