Re: Working copy locked problem

Bolstridge, Andrew wrote:
> Its wonderful idea in an ideal world that the .svn folders will never be
> touched or deleted but we don't live in that ideal world.
>
> My filesystem is a dangerous place, I have editors and compilers and
> temporary files and all kinds of bad things that might trouble a
> delicate .svn directory. A tool to fix issues (cleanup perhaps?) with
> these would be very useful.

There is such a tool. It's called the repository.

> I've been in situations where subversion has gotten confused with an
> added folder, and the end solution was to delete the entire working tree
> and checkout again, with a fair amount of copying local files to and
> from a temporary directory.

If you had committed your work after every each change worth saving, a
fresh checkout would be an easy solution, not just for you, but for
anyone else working on the code, or to let you pick it up on a different
machine. If you have a 'clean trunk' policy where someone is bothered by
work in progress there, copy to a branch for the intermediate work and
merge it back when appropriate. The point of a revision control system
is that you put your revisions in there.

-- 
   Les Mikesell
    lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org