On Tuesday 21 June 2011 03:11 PM, Julian Foad wrote:
> On Tue, 2011-06-21 at 11:37 +0200, Johan Corveleyn wrote:
>> On Tue, Jun 21, 2011 at 11:34 AM, Arwin Arni<arwin_at_collab.net> wrote:
>>> On Tuesday 21 June 2011 02:51 PM, Daniel Shahaf wrote:
>>>> Please convince me why having svn_client_bisect() is needed.
>>>>
>>>> There are already THREE scripts out there that implement cmdline 'svn
>>>> bisect':
>>>> one on CPAN, one in Peter's Debian package, one that Julian just posted.
>>>> (And we got one sent to the issue tracker a while ago, but the CPAN one
>>>> was more featureful)
>>> Wouldn't having it as a part of our API improve the feature set of all the
>>> clients using it?
>> +1
>>
>> It would be nice to have a standard/good implementation of this in svn
>> core. So it's available to people that don't even have perl (or python
>> or whatever scripting language) installed (90% of my dev colleagues
>> around here :-)).
>>
>> It seems like a useful feature.
> Please be careful to distinguish between having an "svn bisect" command
> in the "svn" client versus having an svn_client_bisect() API in
> libsvn_client. This thread is muddling those two things.
>
> - Julian
>
>
Absolutely. I intend to implement the svn_client_bisect API available as
a part of libsvn_client. I think it is a more robust approach than
merely having a subcommand that does something. In fact, I started off
implementing bisect as bisect.c inside libsvn_client and using
bisect-cmd.c as a caller... and then things went haywire, so I stuck to
bisect-cmd.c. I'm pretty sure I'll figure it out soon enough.
Thanks and Regards,
Arwin Arni
Received on 2011-06-21 12:06:06 CEST