From: Lynne <dev@lynne.ee>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] MAINTAINERS: add Niklas Haas for vf_libplacebo.c
Date: Tue, 29 Mar 2022 01:12:36 +0200 (CEST)
Message-ID: <MzHnMiY--3-2@lynne.ee> (raw)
In-Reply-To: <20220328231337.GC115407@haasn.xyz>
28 Mar 2022, 23:13 by ffmpeg@haasn.xyz:
> On Mon, 28 Mar 2022 22:31:36 +0200 Lynne <dev@lynne.ee> wrote:
>
>> I'm not okay with this. I don't mind anyone pushing approved patches,
>> but I still want to review and have final say on all Vulkan code. Could you
>> change that?
>>
>
> The contents of vf_libplacebo is not "Vulkan code". The only thing
> Vulkan about it is the minimal plumbing between AVFrame and libplacebo,
> most of which is actually already happening inside libplacebo's codebase
> (<utils/libav.h`) where I already have complete control over it.
>
Device creation's still done from the lavu-side of things.
> If anything, I still want to move this filter away from being
> Vulkan-exclusive in the future, which would make it even more decoupled
> from your concern.
>
I explicitly told you that's okay when the filter first got merged,
but you didn't change it back then, and I've been waiting for you
to enable it.
_______________________________________________
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:[~2022-03-28 23:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 18:33 Niklas Haas
2022-03-28 20:14 ` James Almer
2022-03-28 20:31 ` Lynne
2022-03-28 20:44 ` Hendrik Leppkes
2022-03-28 21:13 ` Niklas Haas
2022-03-28 23:12 ` Lynne [this message]
2022-03-29 12:12 ` Niklas Haas
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=MzHnMiY--3-2@lynne.ee \
--to=dev@lynne.ee \
--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