From: Nicolas George via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Zhao Zhili <quinkblack@foxmail.com>,
code+AICQIAH6AETBGCQACBFQCNLF7VBPY3U76D5SFB7AR2NR4CQADMDQIAH42WOYLLADAYAACDQKAAFQCAYGAAAQKBAA7ZOYQ@ffmpeg.org,
Kieran Kunhya <kieran618@googlemail.com>,
Nicolas George <george@nsup.org>
Subject: [FFmpeg-devel] Re: Soliciting sponsorship (was: WIP: avfilter: add Bungee audio stretch filter (PR #20697))
Date: Thu, 16 Oct 2025 11:58:24 +0200
Message-ID: <aPDBwGFSA7paiBXd@phare.normalesup.org> (raw)
In-Reply-To: <CABGuwEks_YUCYQidqnq02ACcDikNpXV2SrWfaxz51V=cQsnBeA@mail.gmail.com>
Kieran Kunhya via ffmpeg-devel (HE12025-10-14):
> We should just let people have their libXXX fork of FFmpeg on Forgejo
> in my opinion if we don't want to upstream the code.
This is precisely why Michael added the source plugin mechanism that you
criticized so much.
Regards,
--
Nicolas George
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next prev parent reply other threads:[~2025-10-16 9:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <FFmpeg/FFmpeg/pulls/20697@code.ffmpeg.org>
[not found] ` <reply-AICQIAH6AETBGCQACBFQCNLF7VBPY3U76D5SFB7AR2NR4CQADMDQIAH42WOYLLADAYAACDQKAAFQCAYGAAAQKBAA7ZOYQ@code.ffmpeg.org>
[not found] ` <FFmpeg/FFmpeg/pulls/20697/comment/11972@code.ffmpeg.org>
2025-10-14 10:32 ` [FFmpeg-devel] " Nicolas George via ffmpeg-devel
2025-10-14 10:53 ` [FFmpeg-devel] " Kieran Kunhya via ffmpeg-devel
2025-10-14 11:39 ` Zhao Zhili via ffmpeg-devel
2025-10-14 12:22 ` Kieran Kunhya via ffmpeg-devel
2025-10-16 9:58 ` Nicolas George via ffmpeg-devel [this message]
2025-10-14 16:26 ` Michael Niedermayer via ffmpeg-devel
2025-10-14 17:02 ` Michael Niedermayer via ffmpeg-devel
2025-10-15 11:04 ` Rémi Denis-Courmont via ffmpeg-devel
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=aPDBwGFSA7paiBXd@phare.normalesup.org \
--to=ffmpeg-devel@ffmpeg.org \
--cc=code+AICQIAH6AETBGCQACBFQCNLF7VBPY3U76D5SFB7AR2NR4CQADMDQIAH42WOYLLADAYAACDQKAAFQCAYGAAAQKBAA7ZOYQ@ffmpeg.org \
--cc=george@nsup.org \
--cc=kieran618@googlemail.com \
--cc=quinkblack@foxmail.com \
/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