[llvm-dev] Coverity Scan Needs to be Updated after GitHub Migration

[Mehdi AMINI via llvm-dev]

I use to be subscribed to the weekly report and I was actually addressing
regressions.
The annoying part is the large number of false positive that needed
triage...

On Thu, Jun 3, 2021 at 2:00 PM Luke Benes via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

> > * it was often regressing
> If there is interest, I'd be willing to help with the cov-build,
>
> > * afaik, nobody but me was paying attention to newly detected defects
> (if I am wrong, please let me know and I can have a look).
> In my experience, a weekly report of new defects helps keep engagement up
> and issues down. Here is an example:
>
>
> http://document-foundation-mail-archive.969070.n3.nabble.com/New-Defects-reported-by-Coverity-Scan-for-LibreOffice-td4301033.html
>
> Would a weekly scan report be welcome here?
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210603/31c65052/attachment.html>