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

Re: Meaning of --depth=immediates when deleting a tree [was: [PATCH] Make "update" check a dir for local mods before deleting it.]

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Tue, 14 Oct 2008 23:15:47 +0200

Julian Foad wrote:
> Karl Fogel wrote:
>> Julian Foad <julianfoad_at_btopenworld.com> writes:
>>> $ svn update --depth=immediates # tries to delete A/...
>>> svn: Unable to lock 'A/B'
>>> This errors out because the "update" command puts a write lock only up
>>> to the depth of "immediates", but then the scan for modifications needs
>>> at least a read lock to depth infinity inside "A/".
> I worked around that and committed r33583 to make "update" test the
> whole deep directory tree, even with "--depth=immediates".

"test"? Did you mean "lock"?

Would it not have been sufficient to just lock infinitely on an as-needed
basis (like, when a directory deletion comes across the wire)? (And is that
trivially do-able?)

C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Received on 2008-10-14 23:16:15 CEST

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