I was wondering if this has already been addressed. I didn't see it
in the issue tracker but then I might have missed it.
basically the issue is this. Now that svn is being used more and more
to manage art assets it is in the hands of less technically savvy
users. Those users, especially on Windows, don't know all the rules
they have to follow. So for example, (I'm in the game industry).
Let's say an artist has a folder structure like this
Ogre
--Models
--Textures
This folder is versioned by svn.
Now lets say they want to make Ogre-Commander which is the same Ogre
with a few things changed. So, doing the natural thing, they copy the
folder. They go to Windows Explorer, select the folder "Ogre", copy
and paste, then rename it "Ogre-Commander" and proceed to edit.
The problem is that copy operation also copied all the .svn folders
and now svn is effectively messed up for them and they have to go find
some techincal person to fix this for them.
It would seem like the arguably best though I'm sure unpopular
solution would be to stop storing whatever data is in the .svn folders
locally in each versioned folder. Put them in local database keyed on
the folder name OR put them in a semi mirrored folder tree stored in
like "application data\subversion"
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 2 09:12:05 2005