> On Thursday 08 February 2007 07:00, Erik Hemdal wrote:
> > But if the .svn directory is damaged, it doesn't work, and Tortoise
> > tries to export from the repository. I can't see how it could do
> > anything else, so there's no complaint. If we need to do this, it
> > would be because the WC has been mangled. So it's not exactly the
> > solution to the problem I face. I'd want to do this
> because my WC is
> > broken and I need to salvage local modifications.
>
> Given that the original problem here is that some file trees cannot
> (at least in a practical way) keep the .svn subfolders integrated
> into the tree, why doesn't Subversion offer relocating the .svn tree?
> In other words, there could be a commandline option to svn whith path
> to a different base for .svn files than the target path of the WC. In
> the .svn tree would be the same directory structure as WC, but
> only .svn information in each subdirectory.
Hi,
I strongly support this suggestion.
Actually I already wanted to suggest this myself;
The software we are developing has a customer specific configuration area
that
consists of a sometimes very large directory tree.
Since we are also mirroring customer environments at our place and use SVN
to
version these, our cunsultants often haven the problem of having to take
care of those .svn directories placed within the configuration tree.
It would be very, very helpful if there is an option
to somehow put the .svn directories out-of-place.
Just wanted to jump in on that...
Regards,
Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 22 16:26:18 2007