From: Nicolas George via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Nicolas George <george@nsup.org>
Subject: [FFmpeg-devel] Re: [PATCH] lavfi/mpdecimate: fix three bugs in keep_count logic
Date: Thu, 26 Feb 2026 10:40:24 +0100
Message-ID: <aaAVCG6gfP8MmgzM@phare.normalesup.org> (raw)
In-Reply-To: <DM4PR08MB82450C32687189E3881C11BA8675A@DM4PR08MB8245.namprd08.prod.outlook.com>
Dana Feng via ffmpeg-devel (HE12026-02-25):
> Thanks! Is there a way to get it reviewed / merged? I opened one here: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/22261
Hi. The person who sent you to forgego (who, afaik, is not a regular
FFmpeg contributor) wasted your time: there are no more people capable
and willing to review your patch over there than here. In fact there are
at least one fewer such people.
I do not know if I can gather the motivation to review this patch, my
personal energy has been utterly crushed in the last two weeks. But I
can try a few comments.
It would be helpful to have test-cases, commands to show the difference
your patch makes.
Also, it seems your patch makes three related but independent changes.
Could you split them into three successive patches? That makes it easier
to verify that each change is for the better.
Regards,
--
Nicolas George
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
prev parent reply other threads:[~2026-02-26 9:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 21:37 [FFmpeg-devel] " Dana Feng via ffmpeg-devel
2026-02-18 21:54 ` [FFmpeg-devel] " Dana Feng via ffmpeg-devel
2026-02-18 22:00 ` hassan hany via ffmpeg-devel
2026-02-18 22:05 ` Dana Feng via ffmpeg-devel
2026-02-18 22:12 ` hassan hany via ffmpeg-devel
2026-02-25 15:00 ` Dana Feng via ffmpeg-devel
2026-02-25 15:12 ` Dana Feng via ffmpeg-devel
2026-02-26 9:40 ` Nicolas George via ffmpeg-devel [this message]
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=aaAVCG6gfP8MmgzM@phare.normalesup.org \
--to=ffmpeg-devel@ffmpeg.org \
--cc=george@nsup.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