Philip Martin <philip@codematters.co.uk> writes:
> > This seems to be saying you agree with my proposal to deprecate, then.
>
> It might be a little premature, Subversion itself is still using the
> non-depth interface.
The 'depth' parameter introduced in svn_wc_adm_*_depth doesn't really
correspond to the '--depth' option we've talked about in the past.
Maybe that's an argument for renaming the parameter... Or a parameter
for renaming the argument?
Excuse me, I get carried away sometimes.
Anyway, I think that despite both using the word "depth", these two
things aren't really tied to each other. From svn_wc.h:
* @a depth specifies how much to lock. Zero means just the specified
* directory. Any negative value means to lock the entire working copy
* directory hierarchy under @a path. A positive value indicates the number of
* levels of directories to lock - 1 means just immediate subdirectories, 2
* means immediate subdirectories and their subdirectories, etc. All the
* access batons will become part of the set containing @a adm_access. This
* is an all-or-nothing option, if it is not possible to lock all the
* requested directories then an error will be returned and @a adm_access will
* be invalid, with the exception that subdirectories of @a path that are
* missing from the physical filesystem will not be locked and will not cause
* an error. The error @c SVN_ERR_WC_LOCKED will be returned if a
* subdirectory of @a path is already write locked.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 9 00:20:11 2004