From: Vittorio Giovara <vittorio.giovara@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [WIP] False positives on Coverity Date: Mon, 10 Jun 2024 14:45:14 +0200 Message-ID: <CABLWnS9uJ6i60cGzTEa0YCZcDAhX8oK3wwyW-e-icy_yd4VLcA@mail.gmail.com> (raw) In-Reply-To: <10ec29d6-debe-4f4e-8eb0-4b62103fb554@rothenpieler.org> On Mon, Jun 10, 2024 at 2:41 PM Timo Rothenpieler <timo@rothenpieler.org> wrote: > > In either case, my point is that email is not a good system for these > > reports, because they cannot be tracked nor analyzed, and if they do > pose a > > security risk they shouldn't be advertised so openly. Having a small > bounty > > with STM funds would probably be a more efficient way at fixing them than > > asking people to take a look at them on the ML. > > I'm not sure what you mean. > E-Mail is not the primary system for these reports. > I'm referring to Micheal's email with the list of latest reports. They're just notifications about new stuff, with a rough summary of each > issue, if there aren't too many. > The primary way to track and handle them is via their website. > Again, the one that not everybody has access to, despite being available. If there is any actual interest in fixing them I'm saying we should make them more visible and more accessible, that's all. If they are mostly false positives, then why are we even talking about them? -- Vittorio _______________________________________________ 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-10 12:45 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 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 [this message] 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=CABLWnS9uJ6i60cGzTEa0YCZcDAhX8oK3wwyW-e-icy_yd4VLcA@mail.gmail.com \ --to=vittorio.giovara@gmail.com \ --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