A customer asked if we could provide a recursive "svn unlock" command -- presently they script it. Someone else asked in 2009 -- <http://svn.haxx.se/users/archive-2009-08/0354.shtml>.
It sounds totally reasonable to me. In fact it sounds like an oversight that we didn't offer this originally. Of course we'd want to implement this for URLs and for WC paths, and for all the 'depth' variants not just 'infinite', for consistency. I would propose that "svn lock/unlock --depth=D URL" means lock/unlock all existing files (not directories) under URL down to depth D. "svn lock/unlock --depth=D WC-PATH" means lock/unlock all the versioned files (not directories) in the WC under WC_PATH up to depth D. With regard to recursing into externals, switched paths, etc., this should use the same recursion rules as some other command; not sure which exactly. The main performance considerations would seem to be: Philip recently implemented batching of multiple lock/unlock requests in one network command, which should make multiple lock/unlock requests much better than before; it would still be slow with old servers; but it won't be slower than the wrapper script approach. Anything I've missed? - Julian -- Join WANdisco's free daily demo sessions on Scaling Subversion for the Enterprise <http://www.wandisco.com/training/webinars>
