RE: Working copy locked problem

That's a great ideal, but it's not always the easiest solution. In the
case I mentioned before where we dump out a directory tree and files to
represent the configuration of the system, we've decided we're going to
have to dump to a temporary location that people can't commit from then
write a copy program to handle it in order not to wipe out the .svn
folders and properly mark folders for addition and deletion.

-----Original Message-----
From: Ryan Schmidt [mailto:subversion-2007a@ryandesign.com]
Sent: Friday, February 02, 2007 1:11 AM
To: James Oltmans
Cc: users@subversion.tigris.org
Subject: Re: Working copy locked problem

On Jan 31, 2007, at 16:37, James Oltmans wrote:

> Is there any way to have subversion restore the .svn folder for
> these generated folders?

No. Subversion policy is that you are not to touch the .svn folders
or their contents. If you do, the working copy will most likely
break, as you've seen.

-- 
To reply to the mailing list, please use your mailer's Reply To All  
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org