Evgeny Kotkov <[email protected]> writes: > Indeed, I see that non-readonly operations are locking the necessary portions > of the working copy and that 'svn st' reports it if the operation is aborted: > > svn-1.9 co https://svn.apache.org/repos/asf/subversion/trunk/ . > svn-1.9 up -r {2015-05-01} > ^C > svn-1.9 st
To sum this up, I agree that the new behavior of 'svn st' makes sense for users, assuming that libsvn_wc guarantees that a working copy is locked before any write operations — and that's what I observed from a couple of quick tests. Regards, Evgeny Kotkov
