From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [OSS-Fuzz] Have you considered enabling memory sanitizer?
Date: Wed, 17 Jul 2024 11:54:30 +0200
Message-ID: <172121007031.21847.16431951246468833751@lain.khirnov.net> (raw)
In-Reply-To: <20240716121434.GK4991@pb2>
Quoting Michael Niedermayer (2024-07-16 14:14:34)
> > > > Mostly to
> > > > monitor what issues are reported upstream, as we get some reports in
> > > > mpv fuzzing and I never know if I should report it upstream (ffmpeg)
> > > > or it is already found by first-party fuzzing and I shouldn't make
> > > > more noise.
>
> And to that my reply was a "no", iam not agreeing to give access to
> someone who wants to mainly monitor upstream.
What do you think gives you the right to make such decisions on your
own?
--
Anton Khirnov
_______________________________________________
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-07-17 9:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 19:07 Kacper Michajlow
2024-06-26 22:45 ` Michael Niedermayer
2024-06-27 0:50 ` Kacper Michajlow
2024-07-13 21:12 ` Kacper Michajlow
2024-07-14 19:55 ` Michael Niedermayer
2024-07-15 11:32 ` Kacper Michajlow
2024-07-16 12:14 ` Michael Niedermayer
2024-07-17 0:16 ` Kacper Michajlow
2024-07-17 9:54 ` Anton Khirnov [this message]
2024-07-17 12:22 ` Nicolas George
2024-07-17 12:26 ` Vittorio Giovara
2024-07-17 12:39 ` Nicolas George
2024-07-17 13:15 ` Vittorio Giovara
2024-07-15 12:36 ` Vittorio Giovara
2024-07-16 12:25 ` Michael Niedermayer
2024-07-16 13:18 ` Andrew Sayers
2024-07-16 18:52 ` Vittorio Giovara
2024-07-15 13:01 ` epirat07
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=172121007031.21847.16431951246468833751@lain.khirnov.net \
--to=anton@khirnov.net \
--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