From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [WIP] False positives on Coverity
Date: Sun, 9 Jun 2024 00:49:57 +0200
Message-ID: <e1ab7d75-bdad-4c64-b3b7-cb4fd54183d1@rothenpieler.org> (raw)
In-Reply-To: <CABLWnS9F7wT0ikN9viGm8V=ZAoLiSSJg6rUGiKE2EM6=VsHtOw@mail.gmail.com>
On 08.06.2024 21:49, Vittorio Giovara wrote:
> On Sat, Jun 8, 2024 at 6:02 PM Michael Niedermayer <michael@niedermayer.cc>
> wrote:
>
>> On Tue, May 14, 2024 at 01:38:16AM +0200, Michael Niedermayer wrote:
>>> Hi all
>>>
>>> To keep people updated (and as this is not vissible on the ML)
>>> heres my current list of issues marked as false positives / intentional
>> in Mai & April 2024
>>> (in case anyone wants to review, i presume noone wants but just in case)
>>
>> updated list as of today:
>> [...]
>>
Given the insane amount of them, I'm not a fan of that.
It produces more false positives than anything else.
It also has its own internal tracker for them, so flooding any kind of
other issue tracker with it seems just like point spam to me.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2024-06-08 22:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 23:38 Michael Niedermayer
2024-05-14 7:37 ` Tomas Härdin
2024-05-14 11:28 ` Rémi Denis-Courmont
2024-05-15 8:06 ` Tomas Härdin
2024-06-08 16:01 ` Michael Niedermayer
2024-06-08 19:49 ` Vittorio Giovara
2024-06-08 22:49 ` Timo Rothenpieler [this message]
2024-06-09 13:10 ` Vittorio Giovara
2024-06-09 22:04 ` Michael Niedermayer
2024-06-10 12:37 ` Vittorio Giovara
2024-06-10 12:40 ` Timo Rothenpieler
2024-06-10 12:45 ` Vittorio Giovara
2024-06-11 15:46 ` Michael Niedermayer
2024-06-09 22:02 ` Michael Niedermayer
2024-07-11 23:55 ` Michael Niedermayer
2024-07-12 23:20 ` Michael Niedermayer
2024-07-25 14:41 ` Michael Niedermayer
2024-08-12 17:40 ` Michael Niedermayer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e1ab7d75-bdad-4c64-b3b7-cb4fd54183d1@rothenpieler.org \
--to=timo@rothenpieler.org \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git