Re: Working copy locked problem

On Feb 7, 2007, at 08:44, Erik Hemdal wrote:

>> However, there is no
>> limit to what you can do to the .svn contents and no way for
>> the system
>> to tell or fix that short of comparing to what a fresh copy would
>> contain, which would end up being more work than just making
>> that fresh
>> copy in the first place. Can you suggest a practical mechanism that
>> would help?
>
> A mechanism to find and remove all the .svn directories in a
> working copy
> would help. That wouldn't really repair anything but would at
> least result
> in clean local files that you could put into a fresh WC. I can see
> that
> this is clearly a client-side thing, but something that was part of
> Subversion would be nicer than a script that individuals wrote
> themselves.

You can do this with svn export:

svn export /path/to/working-copy /path/to/export

However I don't know what happens if the working copy has
modifications -- does it export the modified files or the unmodified
files?

You can also easily remove all .svn directories using a find construct:

cp -RPp /path/to/working-copy /path/to/export
find /path/to/export -type d -name .svn -print0 | xargs -0 rm -rf

Or with rsync:

cd /path/to/working-copy
rsync --archive --cvs-exclude . /path/to/export

-- 
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