RE: svn commit: r1431633 - in /subversion/trunk/subversion: libsvn_wc/cleanup.c libsvn_wc/wc_db.c libsvn_wc/wc_db.h tests/cmdline/wc_tests.py
From: Bert Huijben <bert_at_qqmail.nl>
Date: Fri, 11 Jan 2013 14:12:26 +0100
> -----Original Message-----
During WC-NG development we explicitly decided not to do this, because some users run operations on different parts of their working copy at once.
$ svn up wc/branches/subdir
These can run simultaneously.
This was an explicitly supported scenario in 1.6 and earlier.
If one of these commands would break down, you would call 'svn cleanup' on just that target. For 1.7 this still removes the working copy lock and runs the workqueue.
For WC-NG there are certain operations you can't do without a full working copy lock: e.g. cleaning pristines while somebody else has a lock (or when there are wq items)
Your change made it much easier to perform these very dangerous operations, breaking the lock of the second process, while the normal cleanup probably already worked.
This is an archived mail posted to the Subversion Dev mailing list.