fwiw, I'd be supportive of developing obliterate functionality within
trunk, as long as it is not visible at the cmdline (of any tools) for
non-developers. e.g. wrap with #ifdef SVN_DEBUG. (or maybe an
SVN__HAS_OBLITERATE for easier location, later)
For the APIs, I think they could go into things like include/private/
until they're ready to be public.
Cheers,
-g
On Fri, Oct 2, 2009 at 03:26, Julian Foad <julianfoad_at_btopenworld.com> wrote:
> Author: julianfoad
> Date: Fri Oct 2 00:26:11 2009
> New Revision: 39745
>
> Log:
> * subversion/svn/cl.h
> Revert an unwanted part of r39744.
>
> Modified:
> trunk/subversion/svn/cl.h
>
> Modified: trunk/subversion/svn/cl.h
> URL: http://svn.collab.net/viewvc/svn/trunk/subversion/svn/cl.h?pathrev=39745&r1=39744&r2=39745
> ==============================================================================
> --- trunk/subversion/svn/cl.h Fri Oct 2 00:24:52 2009 (r39744)
> +++ trunk/subversion/svn/cl.h Fri Oct 2 00:26:11 2009 (r39745)
> @@ -254,7 +254,6 @@ svn_opt_subcommand_t
> svn_cl__mergeinfo,
> svn_cl__mkdir,
> svn_cl__move,
> - svn_cl__obliterate,
> svn_cl__patch,
> svn_cl__propdel,
> svn_cl__propedit,
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=495&dsMessageId=2402769
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2404749
Received on 2009-10-08 02:35:15 CEST