From: Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Kieran Kunhya <kieran618@googlemail.com>
Subject: Re: [FFmpeg-devel] Plugins architecture
Date: Tue, 12 Aug 2025 13:08:15 -1000
Message-ID: <CABGuwE=1ELiLWAM9+H+eTjeV2HOzAgfCYS+GUh8Fn3vkhBRqXA@mail.gmail.com> (raw)
In-Reply-To: <20250812141052.GK29660@pb2>
On Tue, 12 Aug 2025, 04:11 Michael Niedermayer, <michael@niedermayer.cc>
wrote:
> Hi Lynne
>
> On Mon, Aug 11, 2025 at 09:22:26PM +0900, Lynne wrote:
> > Recently, the issue of plugins was raised.
> >
> > Michael pushed a patch to enable out of tree branches to be freely added
> to
>
> please look at this before you freak out and insta revert things again:
> https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20225
>
> its just a bugfix and spliting the list into a seperat file, i think you
> wont disagree
> but hey i also thought the documentation would not offend anyone
>
> thx
>
How do plugins manage FATE tests?
Kieran
>
_______________________________________________
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".
prev parent reply other threads:[~2025-08-12 23:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 12:22 Lynne
2025-08-11 12:43 ` Michael Niedermayer
2025-08-12 6:25 ` Lynne
2025-08-12 11:35 ` Michael Niedermayer
2025-08-11 13:10 ` Michael Niedermayer
2025-08-11 17:48 ` Jacob Lifshay
2025-08-12 6:38 ` Lynne
2025-08-12 11:59 ` Michael Niedermayer
2025-08-12 14:13 ` [FFmpeg-devel] Global state and mutable component lists (was: Plugins architecture) Nicolas George
2025-08-11 17:38 ` [FFmpeg-devel] Plugins architecture Jacob Lifshay
2025-08-12 12:34 ` Michael Niedermayer
2025-08-12 13:44 ` Nicolas George
2025-08-12 14:10 ` Michael Niedermayer
2025-08-12 23:08 ` Kieran Kunhya 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='CABGuwE=1ELiLWAM9+H+eTjeV2HOzAgfCYS+GUh8Fn3vkhBRqXA@mail.gmail.com' \
--to=ffmpeg-devel@ffmpeg.org \
--cc=kieran618@googlemail.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