On Wed, Feb 22, 2012 at 8:42 AM, Philip Martin
> Mark Phippard <markphip_at_gmail.com> writes:
>> On Wed, Feb 22, 2012 at 4:25 AM, Philip Martin
>> <philip.martin_at_wandisco.com> wrote:
>>> The user has more information than the application can ever have. If
>>> the user wants to be able to run two subtree updates in parallel then
>>> exlusive locking must not be enabled. If the user wants to run status
>>> during an update then exclusive locking must not be enabled.
>> These scenarios are already changes that SQLite brings us. You cannot
>> update two subtrees in parallel today. You cannot run status while an
>> update or commit is running. As noted in another thread this week,
>> you cannot even run svn log when one of these processes is running.
> 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.
I will note that svn log worked fine for me. So I wonder why it did
not for this user:
Could it work differently on Windows?
> 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:
$ svn up
svn: E155004: Working copy '/Users/markphip/work/svnedge' locked.
svn: E155004: '/Users/markphip/work/svnedge/branches' is already locked.
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
Received on 2012-02-22 14:53:57 CET