On Thu, Oct 16, 2014 at 8:53 PM, Gilles Caulier <caulier.gil...@gmail.com> wrote: > Allen,
Hi Gilles, > > Just a workflow question : why to export Coverity report to CSV where > you can send automatically a mail to devel mailing list when scan is > complete, with a a list of new defect found in code. > > I use Coverity since more than one year with whole digiKam code, and > we have already fixed more than 500 entries detected. The Coverity web > interface is really more suitable than a export to CSV. Defect are > very well explained in source context, with all conditions used to > check implementation. > > The only constrain is to have an account for each contributors who > will fixed entries. I suspect that is why Allen is sending out the HTML/CSV output - because not everyone has access and it is helpful to have this information publicly accessible. > > After one year to use this tool, the feedback is really excellent, > especially to check new code from students. > > Best > > Gilles Caulier Thanks, Ben > > 2014-10-14 14:30 GMT+02:00 Allen Winter <allen.d.win...@gmail.com>: >> Howdy, >> >> Attached is the Coverity Scan report for kdepimlibs 4.14 as of today. >> You might feel like fixing some of the issues. >> >> Let me know if you find false positives or stuff we can ignore (like in test >> programs).
