Re: Need more Functionality :)

On Feb 17, 2005, at 4:52 AM, Bert wrote:

> 4) A "write" access denied seems to lock the working copy (only the
> just above directory of the error). For example, an subdir as different
> user owner. The workarround is to edit by hand the .svn/entries of the
> dir containing the bad subdir and delete any reference to that subdir.
> Svn commit into database is atomic, but svn command on the working
> commit are not. Am I the only one to get that sort of problem, not the
> bad user owner (that is a bad administration of the wc) but the crash
> of
> 'svn add' (or 'import') that need human work ?
> => atomic operation on the working copy ?

I have been bitten by this multiple times. Usually as a result of
manually migrating some projects from Visual Source Safe, where files
are usually set read-only when you get a working copy.

I've brought it up on this list twice, but those posts have been
ignored. :(

It seems it is fairly easy to corrupt the working copy with a simple
mistake, whereas the repository is well protected.

Scott

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Feb 19 22:36:58 2005