The new svn_client_mtcc API

2014-07-29 Thread Julian Foad
I just looked at svn_client_mtcc.h, scheduled for 1.9 release I noticed it's basically an svn_delta_editor commit editor at the libsvn_client level, without the 'open' and 'close' methods. The header file doesn't say anything about the semantics and rules for the provided functions. I'm guessin

Re: The new svn_client_mtcc API

2014-07-29 Thread Branko Čibej
On 29.07.2014 12:27, Julian Foad wrote: > I just looked at svn_client_mtcc.h, scheduled for 1.9 release > > I noticed it's basically an svn_delta_editor commit editor at the > libsvn_client level, without the 'open' and 'close' methods. > > The header file doesn't say anything about the semantics

Re: The new svn_client_mtcc API

2014-07-29 Thread Greg Stein
On Tue, Jul 29, 2014 at 5:45 AM, Branko Čibej wrote: > On 29.07.2014 12:27, Julian Foad wrote: > > I just looked at svn_client_mtcc.h, scheduled for 1.9 release > > I noticed it's basically an svn_delta_editor commit editor at the > libsvn_client level, without the 'open' and 'close' methods. >

Re: The new svn_client_mtcc API

2014-07-29 Thread Julian Foad
[Brane and Greg said +1.] Bert, I'm CC'ing to you as you added the code. I'll move the header file into the 'private' subdirectory, in preparation for the 1.9 release, as there is consensus that this is not ready for prime time. Then we can still use it and can work on improving it with no time

Re: The new svn_client_mtcc API

2014-07-29 Thread Branko Čibej
On 29.07.2014 19:32, Julian Foad wrote: > [Brane and Greg said +1.] > > Bert, I'm CC'ing to you as you added the code. > > I'll move the header file into the 'private' subdirectory, in preparation for > the 1.9 release, as there is consensus that this is not ready for prime time. > Then we can st

Re: The new svn_client_mtcc API

2014-07-30 Thread Julian Foad
> On 29.07.2014 19:32, Julian Foad wrote: >> I'll move the header file into the 'private' subdirectory, in preparation >> for the >> 1.9 release, as there is consensus that this is not ready for prime time. >> Then we >> can still use it and can work on improving it with no time restriction. Don