From: compn via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: ff@hawaiiantel.net
Subject: [FFmpeg-devel] Re: question about submitting security patches
Date: Wed, 12 Nov 2025 21:36:46 -0800
Message-ID: <8056ce239cf62fe4ccc2a3b86368880d@hawaiiantel.net> (raw)
In-Reply-To: <CA+GtNgk7PHvgS+EJMrxbwHFCMr_tgsYHhjtHdYF-c5pYYj0YZg@mail.gmail.com>
On 2025-11-08 00:34, Thomas Dullien via ffmpeg-devel wrote:
> 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?
>
> Cheers,
> Thomas
the best way is whatever you prefer.
https://code.ffmpeg.org/FFmpeg is the new way.
the mailing list is also OK to post patches.
-compn
compn@ffmpeg.org
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
prev parent reply other threads:[~2025-11-13 5:39 UTC|newest]
Thread overview: 16+ 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
2025-11-11 8:27 ` Gyan Doshi via ffmpeg-devel
2025-11-12 8:09 ` Kieran Kunhya via ffmpeg-devel
2025-11-13 3:06 ` Michael Niedermayer via ffmpeg-devel
2025-11-13 3:52 ` Kieran Kunhya via ffmpeg-devel
2025-11-13 18:38 ` Michael Niedermayer via ffmpeg-devel
2025-11-13 14:50 ` Timo Rothenpieler via ffmpeg-devel
2025-11-13 18:59 ` ff--- via ffmpeg-devel
2025-11-14 7:40 ` Tobias Rapp via ffmpeg-devel
2025-11-12 8:24 ` Christophe Gisquet via ffmpeg-devel
2025-11-12 10:26 ` Thomas Dullien via ffmpeg-devel
2025-11-13 5:36 ` compn 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=8056ce239cf62fe4ccc2a3b86368880d@hawaiiantel.net \
--to=ffmpeg-devel@ffmpeg.org \
--cc=ff@hawaiiantel.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