On Mon, Sep 19, 2011 at 4:29 AM, Jan Safranek <[email protected]> wrote: > On 08/24/2011 01:39 PM, Jan Safranek wrote: >> I've run Coverity check on current git sources and fixed few warnings/errors >> it has found. Usually we leak file descriptors or memory in error cases, >> which were generally not much tested. It's quite a lot of patches, but >> they're >> pretty small and most of them are really simple. >> >> Changelog: >> - removed changes in libcg_ba test, the test going to be removed >> - Patch 3: removed whitespace changes >> - Patch 4: removed error variable >> - Patch 8: reworked to use setjmp/longjmp >> >> Jan > > I've gave up waiting for review and after some testing (mostly 'make > check') I merged the patches in. >
ACK :-). I was confused by the weird numbering of the patches. Dhaval ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Libcg-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libcg-devel
