From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/2] avformat/id3v2: Check that decode_str() did advance
Date: Wed, 16 Apr 2025 02:53:34 +0200
Message-ID: <20250416005334.GD4991@pb2> (raw)
In-Reply-To: <DM8P223MB03654DFB8790C225AC03A3F8BAB22@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>
[-- Attachment #1.1: Type: text/plain, Size: 836 bytes --]
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.
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
The misfortune of the wise is better than the prosperity of the fool.
-- Epicurus
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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:[~2025-04-16 0:53 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 22:27 [FFmpeg-devel] [PATCH 1/2] avformat/id3v2: Print the unknown encoding Michael Niedermayer
2025-04-11 22:27 ` [FFmpeg-devel] [PATCH 2/2] avformat/id3v2: Check that decode_str() did advance Michael Niedermayer
2025-04-12 1:49 ` softworkz .
2025-04-14 23:19 ` Michael Niedermayer
2025-04-14 23:59 ` softworkz .
2025-04-15 0:02 ` Ridley Combs via ffmpeg-devel
2025-04-15 0:17 ` softworkz .
2025-04-15 18:32 ` Michael Niedermayer
2025-04-15 19:03 ` Nicolas George
2025-04-15 20:12 ` softworkz .
2025-04-15 20:47 ` Nicolas George
2025-04-15 22:20 ` softworkz .
2025-04-16 5:15 ` Nicolas George
2025-04-16 5:59 ` softworkz .
2025-04-16 7:02 ` Nicolas George
2025-04-15 19:15 ` softworkz .
2025-04-15 19:02 ` Nicolas George
2025-04-16 8:02 ` Andreas Rheinhardt
2025-04-15 18:55 ` Michael Niedermayer
2025-04-15 19:59 ` softworkz .
2025-04-15 22:50 ` Michael Niedermayer
2025-04-15 22:59 ` softworkz .
2025-04-15 23:01 ` softworkz .
2025-04-16 0:53 ` Michael Niedermayer [this message]
2025-04-16 1:01 ` softworkz .
2025-04-16 2:39 ` softworkz .
2025-04-16 7:04 ` Nicolas George
2025-04-16 11:07 ` Michael Niedermayer
2025-04-16 11:15 ` softworkz .
2025-04-16 1:21 ` Michael Niedermayer
2025-04-16 1:29 ` softworkz .
2025-04-16 1:33 ` Michael Niedermayer
2025-04-16 2:18 ` softworkz .
2025-04-16 2:31 ` softworkz .
2025-04-16 10:41 ` Michael Niedermayer
2025-04-16 10:59 ` softworkz .
2025-04-16 2:52 ` softworkz .
2025-04-16 10:53 ` Michael Niedermayer
2025-04-16 10:57 ` Andreas Rheinhardt
2025-04-16 11:02 ` Michael Niedermayer
2025-04-16 10:58 ` softworkz .
2025-04-15 1:37 ` softworkz .
2025-04-15 18:25 ` Michael Niedermayer
2025-04-15 19:07 ` softworkz .
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=20250416005334.GD4991@pb2 \
--to=michael@niedermayer.cc \
--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