the .svn folder is subversions working copy administrative area - dont mess
with it unless you know what you are doing
the svn client needs that to operate. there are alternatives though, like
steve mentioned, svk stores its metadata other places and theres a way to
use apache and dav to set up a dav share that does an autocommitt on every
PUT
On 2/16/07, nbs <nbs_r@gazeta.pl> wrote:
>
> I have a tool storing its data (electronics design) in a numerous binary
> files distributed over many subdirectories. It generally works well with
> SVN, except for the following issue.
>
> The tool has a GUI for design management, which permits copying, moving,
> renaming and deleting parts of the design. The problem is, all these
> functions operate recursively on whole subdirectories. If the user
> attempts to make a copy of a design part, a '.svn' directory belonging
> to it will be copied as well. This requires the user to manually delete
> '.svn' directory from the newly copied part before adding and commiting
> it to the repository.
>
> How to move all .svn directories out of the working copy directory? Is
> there any configuration option for this? Alternatively, how to prevent
> SVN client failure when it comes across bogus .svn data.
>
> Thank you,
> \R.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
Received on Fri Feb 16 15:47:20 2007