From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] avfilter: POC: enable out-of-tree filters Date: Fri, 14 Mar 2025 21:58:50 +0100 Message-ID: <20250314205850.GN4991@pb2> (raw) In-Reply-To: <66647849-682a-45d1-8015-e6173a8e51f8@gmail.com> [-- Attachment #1.1: Type: text/plain, Size: 1408 bytes --] On Fri, Mar 14, 2025 at 05:13:23PM +0100, Leandro Santiago wrote: [...] > > > > also there is the quite intriguing option of using "git merge" to include > > external filters > > What i mean here is that there could be a script lets call it ffmerge > How would it work when using release tarballs, without git? it would tell the user to run it in a git checkout or an empty directory. The script would already have the ability to merge external filter repos so also pulling mainline is no real extra complexity > > "ffmerge available" would check some online repository and list whats > > compatible with the current checkout > > > > "ffmerge merge shiny_filter" would then merge the shiny filter repository/branch > Wouldn't it put more burden over the devs to maintain such > catalog/repository and the tooling around it? I am fine with that, I just > wonder how the community would accept it. Having no filter catalog/repo > feels to be the simplest step one could take at the moment. theres no need for such catalog. I just think that if external filter support is added, that someone will then likely start maintaining a catalog of these filters. thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws. -- Plato [-- 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-03-14 20:59 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-03-13 12:18 Leandro Santiago 2025-03-13 12:20 ` Leandro Santiago 2025-03-14 15:04 ` Michael Niedermayer 2025-03-14 16:13 ` Leandro Santiago 2025-03-14 20:58 ` Michael Niedermayer [this message] 2025-03-14 16:57 ` Lynne 2025-03-14 18:21 ` Nicolas George 2025-03-14 19:43 ` Leandro Santiago 2025-03-14 22:45 ` Soft Works
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=20250314205850.GN4991@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