[Zdenek Styblik] >> Is the Coverity scanning something that should be done regularly? > > I'm not sure how good or effective Coverity is, but something is > better than nothing. Let's roll with yes then?
Coverity is said to have discovered heaps of security and stability issues with free software like the Linux kernel, and is generaly believed to do a very good job at finding some classes of security and stability bugs. A quick search sent me to <URL: http://www.linuxinsider.com/story/79071.html >, <URL: http://www.coverity.com/library/pdf/coverity_linuxsecurity.pdf > and <URL: http://cacm.acm.org/magazines/2010/2/69354-a-few-billion-lines-of-code-later/fulltext > providing background information. Just to be sure: Is the CVS the authorative source? (Time to move to git?) How often should it be checked? There is a limit which I believe is no more than three times a week. I've added jman as a "contributor/member", whatever that role means. It was the only pending request to get access to the results. So far Sebastien Bouchard, me and jman have access to the scan result, and Sebastien Bouchard and me can submit new builds. -- Happy hacking Petter Reinholdtsen ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ Ipmitool-devel mailing list Ipmitool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
