Is there a reason the get lock report does not support a "depth"
concept and just reports all locks "at or below" the specified
path?

I noticed on a large repository with a large number of
locks, this report can be many megabytes worth of
(worthless) network transmitted data when doing a
simple non-recursive "svn ls -v http://server/repo/";
command.

Since the get-locks-report is already custom, does
this sound like an easy (and useful) addition?

I tested with 1.6.5 using apache 2.2.12, but I
don't think anything has changed in this
area recently...

Kevin R.

Reply via email to