From: Dale Curtis <dalecurtis@chromium.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] [h264] Make slice header parse errors fatal under AV_EF_EXPLODE
Date: Fri, 24 Jan 2025 10:49:33 -0800
Message-ID: <CAPUDrwersxni-tkDeBAM2R=o7qTaYuwr5s+9qan18uwTMzVieA@mail.gmail.com> (raw)
In-Reply-To: <20250113005825.GT4991@pb2>
Any more comments for this one? Thanks!
- dale
On Sun, Jan 12, 2025 at 4:58 PM Michael Niedermayer <michael@niedermayer.cc>
wrote:
> Hi Marth64
>
> On Wed, Jan 08, 2025 at 12:44:15AM -0600, Marth64 wrote:
> > It makes sense based on the surrounding code and AV_EF_EXPLODE use case.
> > Will let it sit for a few days for others to provide feedback.
>
> the patch looks correct to me too, only took a quick look though
>
> thx
>
> [...]
>
> --
> Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
>
> The smallest minority on earth is the individual. Those who deny
> individual rights cannot claim to be defenders of minorities. - Ayn Rand
> _______________________________________________
> 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".
>
_______________________________________________
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 parent reply other threads:[~2025-01-24 18:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPUDrwepF3yhLsXuhigYQdA9YzNHvT7oC8_Q2Yeyij1yJP9dSQ@mail.gmail.com>
[not found] ` <CA+28BfBrPZ2i7az2DCmX1x5tcrLE_p_c1Uovw+=paoPZMtVx8Q@mail.gmail.com>
[not found] ` <20250113005825.GT4991@pb2>
2025-01-24 18:49 ` Dale Curtis [this message]
2025-01-25 1:33 ` Marth64
2025-01-30 4:38 ` Marth64
2025-02-03 2:43 ` Marth64
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='CAPUDrwersxni-tkDeBAM2R=o7qTaYuwr5s+9qan18uwTMzVieA@mail.gmail.com' \
--to=dalecurtis@chromium.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