[FFmpeg-devel] [PATCH 2/2] avformat/id3v2: Check that decode_str() did advance
softworkz .
softworkz at hotmail.com
Wed Apr 16 04:01:26 EEST 2025
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces at ffmpeg.org> On Behalf Of
> Michael Niedermayer
> Sent: Mittwoch, 16. April 2025 02:54
> To: FFmpeg development discussions and patches <ffmpeg-
> devel at ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH 2/2] avformat/id3v2: Check that
> decode_str() did advance
>
> On Tue, Apr 15, 2025 at 11:01:14PM +0000, softworkz . wrote:
> [...]
> > Besides, the patch had been submitted 3 years ago, there hasn't been
> > any review and the merge was totally unexpected.
>
> no reply for 1 week means commit must be expected
>
> "Send a patch to ffmpeg-devel. If no one answers within a reasonable
> time-frame (12h for build failures and security fixes, 3 days small
> changes,
> 1 week for big patches) then commit your patch if you think it is OK.
> Also note, the maintainer can simply ask for more time to review!
> "
>
> besides, i reviewed the patch before applying it
>
> and there was an open bug that alot of people wanted fixed.
But not in a way that breaks their deserialization or parsing.
Essentially, you've just exchanged this bug for another way more severe
bug in the FFprobe output. Do you just want to await the reports
and complaints coming in?
No matter whether applying this patch was OK or not in the first place,
knowing that it causes a serious regression doesn't appear to me like
something that could just be ignored, or do you think otherwise?
sw
More information about the ffmpeg-devel
mailing list