On 10/04/2012 07:57 PM, breser_at_apache.org wrote:
> Author: breser
> Date: Thu Oct 4 23:57:26 2012
> New Revision: 1394332
> Modified: subversion/trunk/subversion/include/svn_client.h
> URL: http://svn.apache.org/viewvc/subversion/trunk/subversion/include/svn_client.h?rev=1394332&r1=1394331&r2=1394332&view=diff
> --- subversion/trunk/subversion/include/svn_client.h (original)
> +++ subversion/trunk/subversion/include/svn_client.h Thu Oct 4 23:57:26 2012
> @@ -1469,10 +1469,9 @@ svn_client_switch(svn_revnum_t *result_r
> * If @a force is not set and @a path is already under version
> * control, return the error #SVN_ERR_ENTRY_EXISTS. If @a force is
> - * set, do not error on already-versioned items. When used on a
> - * directory in conjunction with the @a recursive flag, this has the
> - * effect of scheduling for addition unversioned files and directories
> - * scattered deep within a versioned tree.
> + * set, do not error on already-versioned items. When used with @a depth
> + * set to #svn_depth_infinity it will enter versioned directories; scheduling
> + * versioned children.
"scheduling versioned children" doesn't really parse for me in this context
semantically. Also, the semicolon that precedes the phrase is not the
proper punctuation for offsetting such a thing.
Perhaps you meant something like:
"... it will enter versioned directories, scheduling any unversioned
children thereof for addition."
But why only #svn_depth_infinity? Will it not do the same (to different
depths, of course) for #svn_depth_files and #svn_depth_immediates?
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet <> www.collab.net <> Enterprise Cloud Development
Received on 2012-10-05 03:46:52 CEST