From: "Rémi Denis-Courmont via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches
<ffmpeg-devel@ffmpeg.org>,
Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
Cc: "Michael Niedermayer" <michael@niedermayer.cc>,
"Rémi Denis-Courmont" <remi@remlab.net>
Subject: [FFmpeg-devel] Re: question about submitting security patches
Date: Tue, 11 Nov 2025 08:49:49 +0200
Message-ID: <F775A075-688D-47EF-AB96-6853263D761F@remlab.net> (raw)
In-Reply-To: <aRKmnnDyzp4maRzq@neo>
Le 11 novembre 2025 04:59:42 GMT+02:00, Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> a écrit :
>Hi Remi
>
>On Mon, Nov 10, 2025 at 06:03:38PM +0200, Rémi Denis-Courmont via ffmpeg-devel wrote:
>> Le lauantaina 8. marraskuuta 2025, 10.34.24 Itä-Euroopan normaaliaika Thomas
>> Dullien via ffmpeg-devel a écrit :
>> > What's the best way to submit these patches? There is the bug tracker,
>> > there is this mailing list - what's the best way to contribute them?
>>
>> I don't think that DNN-generated patches are compatible with the LGPL in the
>> first place, or it is at best very uncertain that they are. So then you cannot
>> contribute DNN-generated patches in any useful way at all.
>
>If you have concrete legal analysis or case law that supports this claim, please share it.
You can check what LF, Fedora, QEMU, etc, and their lawyers already did on that front.
_______________________________________________
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-11-11 6:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-08 8:34 [FFmpeg-devel] " Thomas Dullien via ffmpeg-devel
2025-11-10 16:03 ` [FFmpeg-devel] " Rémi Denis-Courmont via ffmpeg-devel
2025-11-10 16:19 ` Thomas Dullien via ffmpeg-devel
2025-11-11 2:59 ` Michael Niedermayer via ffmpeg-devel
2025-11-11 6:49 ` Rémi Denis-Courmont via ffmpeg-devel [this message]
2025-11-11 8:27 ` Gyan Doshi 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=F775A075-688D-47EF-AB96-6853263D761F@remlab.net \
--to=ffmpeg-devel@ffmpeg.org \
--cc=michael@niedermayer.cc \
--cc=remi@remlab.net \
/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