> The "depth" parameter is used in many places, not just in "svn list"; whatever enhancement you come up with must at least fit the other uses. Depth was invented to describe sparse working copies, and was only later adapted to other commands. For sparse working copies, "depth=dirs" probably doesn't make much sense.

> Once you've defined what "depth=dirs" means for all the commands that support depth, you're about 10% done ... you'd have to review the implementation for every use of the depth parameter and either add "depth=dirs" semantics, or make sure a reasonable error message is returned if that value is not supported by a particular command: 

Yeah, I figured this would get shot down pretty quick since I mentioned a modification to a key parameter.  Completely understand and agree.  I've been digging around the API and I'm not sure I even see a call/parameter to fetch a directory listing only from the server.  Does with more knowledge of the API know if the API supports this, if so, any pointers (no pun intended).   I'm glad to call an API directly if that would work.

I'd also assume I won't get much traction with a new parameter unique to the list command (should it even be possible).