[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Issue 864] Changed - 'svn rm --force' a scheduled (not committed) directory tree fails with locking errors

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2002-08-11 21:08:27 CEST

Peter Davis <peter@pdavis.cx> writes:

> I filed two issues, and you incorrectly changed the summary on one of them to
> match the other (maybe you got them confused?) The cleanup problem has
> nothing to do with deleting directories that are missing. It has to do with
> deleting trees (a directory with one or more subdirectories).

Apologies if I got it wrong. It may be the patches I have for issue
749 are giving me different results, but it is fixed in my tree. The
"Working copy not locked" problem looks exactly like the one I fixed
with rev 2938. If it's not fixed now it will get fixed when I check
in my issue 749 patch.

Does 'svn rm --force /path/to/wc/a' work when 'svn rm --force a' fails?

It also helps if you can raise one issue for one problem :-)

Philip Martin
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Aug 11 21:09:09 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.