On 9/2/05, Gregg Tavares <gmansvn@greggman.com> wrote:snip
> 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"
>
> There is work going on to allow working copies to not have a text-base,
but I
don't think that is sufficient for what you need. That's an interesting use
case
that probably should be supported.
I think it should go into the issue tracker. I'm not sure how to fix it. Did
the user
svn add the folder after making the copy? Did that fail? If so then this is
a bug.
What client were they using? Maybe that should be a client supported
behavior
in a GUI?
I, also, didn't see any open bugs for this.
Josh
Received on Fri Sep 2 17:56:35 2005