Re: New Defects reported by Coverity Scan for Wireshark (forw)

[Martin Kaiser <lists () kaiser cx>]

Hi,

Thus wrote Joerg Mayer (jmayer () loplof de):

> I'm receiving coverity reports via email. Unfortunately I don't really have
> the time to look at them most of the time.
> What I might do if there is interest in it: I could open a bug for each
> dissector and copy the contents into the bug.

> Opinions?

I don't see any benefit in copying coverity infos into bugzilla. This
is just additional work and I doubt that this would inspire more people
to look at the defects. The clang analysis reports are publicly
available and don't get much attention either. 

If there's many / severe defects for a dissector and a non-core
developer maintains it, we could notify him.

However, if you find out how to unsubscribe from the notifications,
please let me know ;-)

Best regards,

   Martin
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe