Mihai Danila <virid...@gmail.com> writes: > That's exactly the problem. In SVN 1.6 I was able to run concurrent SVN > updates on different directories. Their separate databases were updateable > separately. In 1.7, this is no longer possible.
Both 1.7 and 1.8 allow concurrent updates but the update targets have to be a bit further apart than 1.6. Given a working copy layout: wc/ wc/A/ wc/A/B/ wc/X/ wc/X/Y/ With 1.6 svn up wc/A/B locks the whole tree for the explict target wc/A/B plus a lock on the parent directory wc/A, while 1.8 locks the whole tree for the parent wc/A. The result is that both 1.6 and 1.8 allow svn up wc/A/B svn up wc/X/Y in parallel, but only 1.6 allows svn up wc/A svn up wc/X/Y in parallel, and neither allows svn up wc/A svn up wc/X in parallel. -- Philip Martin | Subversion Committer WANdisco // *Non-Stop Data*
