Re: svn commit: r1648253 - /subversion/trunk/subversion/libsvn_fs_fs/tree.c

2014-12-29 Thread Evgeny Kotkov
Stefan Fuhrmann writes: > In FSFS, use sub-pools for temporaries in those API function implementations > that call open_path(). > > All these functions are complex enough to make the overhead of creating a > temporary sub-pool be outweighed by the benefits of tighter memory usage and > better iso

[RFC] Refining our naming rules

2014-12-29 Thread Stefan Fuhrmann
Hi there, FSX code contains various violations to our naming rules, mostly taken over FSFS. I thought about a scheme that complies to our rules but also refines them. I'd like to amend our coding guideline with the following suggestions (not as a strict requirement). The first one is actually "ne

ruby 2.2: check-swig-rb test fails

2014-12-29 Thread Anatol Pomozov
Hi I am trying to compile/run 1.8.11 svn tests with recently released ruby 2.2 and ruby swig test fails. See the output below. Looking at run-test.rb code I do not see anything obviously wrong. Can anybody reproduce the same problem? [anatol@argo subversion-1.8.11]$ make check-swig-rb if [ "LD

Re: svn commit: r1648253 - /subversion/trunk/subversion/libsvn_fs_fs/tree.c

2014-12-29 Thread Stefan Fuhrmann
On Mon, Dec 29, 2014 at 1:46 PM, Evgeny Kotkov wrote: > Stefan Fuhrmann writes: > > > In FSFS, use sub-pools for temporaries in those API function > implementations > > that call open_path(). > > > > All these functions are complex enough to make the overhead of creating a > > temporary sub-pool

Re: [RFC] Refining our naming rules

2014-12-29 Thread Branko Čibej
On 29.12.2014 13:59, Stefan Fuhrmann wrote: > Hi there, > > FSX code contains various violations to our naming rules, > mostly taken over FSFS. I thought about a scheme that > complies to our rules but also refines them. > > I'd like to amend our coding guideline with the following > suggestions (n

Re: ruby 2.2: check-swig-rb test fails

2014-12-29 Thread Anatol Pomozov
Hi On Mon, Dec 29, 2014 at 5:19 AM, Anatol Pomozov wrote: > Hi > > I am trying to compile/run 1.8.11 svn tests with recently released ruby > 2.2 and ruby swig test fails. See the output below. Looking at > run-test.rb code I do not see anything obviously wrong. > > Can anybody reproduce the same

[l10n] Translation status report for trunk r1648479

2014-12-29 Thread Subversion Translation Status
Translation status report for trunk@r1648479 lang trans untrans fuzzy obs -- de2872 3 7 490 +~o es2264 611 829 528 ++U~~~ fr2568 307