On 02/18/2011 06:42 AM, Stefan Küng wrote:
> On 17.02.2011 14:19, Hyrum K Wright wrote:
>> Last summer in Berlin we had a quite heated discussion about just
>> deprecating all of libsvn_wc APIs. I was against such a move (at
>> least until 2.0) in that it would leave the existing APIs public, but
>> any new ones private, and the whole interface in limbo. I still feel
>> that way, and this discussion vindicates that feeling (at least to me
>> :) ).
> Removing all the libsvn_wc APIs is a bad idea. For example, the new status
> function returns a *lot* less information than the deprecated ones.
Stop right here. There seems to be an assumption clouding this discussion,
and that assumption is that "the new status function" is the only new status
function that can be added. It's our API -- your API -- and we can do with
it what we wish. If you need the functionality of some current libsvn_wc
function, chances are that you're not the only one who does. Fortunately,
we are both empowered and motivated to provide that functionality to you
wrapped with a thin svn_client wrapper function. Is there some technical
reason that would prevent this?
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on 2011-02-18 14:38:25 CET