On 22 December 2014 at 23:16, Stefan Fuhrmann
wrote:
> On Mon, Dec 22, 2014 at 2:09 PM, Ivan Zhakov wrote:
>>
>> On 19 December 2014 at 19:26, Ivan Zhakov wrote:
>> >
>> > On 19 December 2014 at 18:55, Branko Čibej wrote:
>> > > On 19.12.2014 15:37, Ivan Zhakov wrote:
[...]
>>
>> So the best op
On 2 February 2015 at 18:24, wrote:
> Author: brane
> Date: Mon Feb 2 15:24:16 2015
> New Revision: 1656488
>
> URL: http://svn.apache.org/r1656488
> Log:
> Introduce a private libsvn_client context structure that stores
> context information that should not be part of the public API.
>
> * subv
On 02.02.2015 16:33, Ivan Zhakov wrote:
> On 2 February 2015 at 18:24, wrote:
>> Author: brane
>> Date: Mon Feb 2 15:24:16 2015
>> New Revision: 1656488
>>
>> URL: http://svn.apache.org/r1656488
>> Log:
>> Introduce a private libsvn_client context structure that stores
>> context information tha
On 2 February 2015 at 18:55, Branko Čibej wrote:
> On 02.02.2015 16:33, Ivan Zhakov wrote:
>> On 2 February 2015 at 18:24, wrote:
>>> Author: brane
>>> Date: Mon Feb 2 15:24:16 2015
>>> New Revision: 1656488
>>>
>>> URL: http://svn.apache.org/r1656488
>>> Log:
>>> Introduce a private libsvn_cli
On 02.02.2015 17:09, Ivan Zhakov wrote:
> On 2 February 2015 at 18:55, Branko Čibej wrote:
>> On 02.02.2015 16:33, Ivan Zhakov wrote:
>>> On 2 February 2015 at 18:24, wrote:
Author: brane
Date: Mon Feb 2 15:24:16 2015
New Revision: 1656488
URL: http://svn.apache.org/r16
On 2 February 2015 at 19:17, Branko Čibej wrote:
> On 02.02.2015 17:09, Ivan Zhakov wrote:
>> On 2 February 2015 at 18:55, Branko Čibej wrote:
>>> On 02.02.2015 16:33, Ivan Zhakov wrote:
On 2 February 2015 at 18:24, wrote:
> Author: brane
> Date: Mon Feb 2 15:24:16 2015
> New
On Mon, Feb 2, 2015 at 5:34 PM, Ivan Zhakov wrote:
> On 2 February 2015 at 19:17, Branko Čibej wrote:
> > On 02.02.2015 17:09, Ivan Zhakov wrote:
> >> On 2 February 2015 at 18:55, Branko Čibej wrote:
> >>> On 02.02.2015 16:33, Ivan Zhakov wrote:
> On 2 February 2015 at 18:24, wrote:
> >>
Ivan Zhakov writes:
> We can make changes in HACKING document of course, but we need to
> discuss it first and then update code to match new code style.
Our guidelines are not that rigid. We could choose to use a new style
in new code without updating old code. We could choose to allow more
th
Translation status report for trunk@r1656623
lang trans untrans fuzzy obs
--
de2883 16 23 492 +~o
es2274 625 841 527 ++U~~~
fr2577 322
9 matches
Mail list logo