Mark Phippard <markp...@gmail.com> writes: > On Wed, Feb 22, 2012 at 8:42 AM, Philip Martin > <philip.mar...@wandisco.com> wrote: >> >> That's not correct. Start and hold an update: >> >> $ gdb -arg subversion/svn/.libs/lt-svn up wc/A/B/C >> (gdb) b update_editor.c:close_directory >> (gdb) r >> Breakpoint 2 at 0x7ffff78eee2f >> >> Run status: >> >> $ svn st wc >> L wc/A/B >> ! L wc/A/B/C >> ! L wc/A/B/C/D > > When I do this on my OSX system, I see the the L status for every > folder in my WC. That might technically mean the command is working, > but it is not what I want to see.
Note I updated A/B/C and the parent A/B is locked; this allows for A/B/C to be deleted. This prevents updating another subtree in A/B such as A/B/X but does not prevent the update of a parallel parent such as X/Y/Z. This behaviour is unchanged from 1.6. > > I will note that svn log worked fine for me. So I wonder why it did > not for this user: > > http://mail-archives.apache.org/mod_mbox/subversion-users/201202.mbox/%3C135b01cceead%24cd1d1590%24675740b0%24%40webkr.de%3E > > Could it work differently on Windows? Difficult to say since we don't have any details. It could be blocking and timing out, or it could be seeing a workqueue item. Both of those are new reductions in concurrency in 1.7 >> Update a different subtree: >> >> $ svn up wc/X/Y/Z >> Updating 'wc/X/Y/Z': >> A wc/X/Y/Z/Q >> Updated to revision 4. > > This does not work for me. I have an entire repository checked out > and started an update in my /branches folder and my /trunk folder. > The latter fails: Yes /branches and /trunk will both attempt to lock / to allow for the target to be deleted. You should be able to update /branches/foo and /trunk/subversion. -- uberSVN: Apache Subversion Made Easy http://www.uberSVN.com
