From: moshekaplan <code@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] [PATCH] Update README.md Contributing (PR #20160)
Date: Thu, 7 Aug 2025 19:33:50 +0300 (EEST)
Message-ID: <20250807163350.6813968D16C@ffbox0-bg.ffmpeg.org> (raw)
PR #20160 opened by moshekaplan
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20160
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20160.patch
Update README.md with new location to submit code patches
From b9434c13d17cf0880d079db8f8c9fd16476be991 Mon Sep 17 00:00:00 2001
From: moshekaplan <mosheekaplan@gmail.com>
Date: Thu, 7 Aug 2025 16:33:14 +0000
Subject: [PATCH] Update README.md Contributing
Update README.md with new location to submit code patches
---
README.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/README.md b/README.md
index f8c23f2870..85e0f316d2 100644
--- a/README.md
+++ b/README.md
@@ -41,6 +41,6 @@ GPL. Please refer to the LICENSE file for detailed information.
## Contributing
-Patches should be submitted to the ffmpeg-devel mailing list using
-`git format-patch` or `git send-email`. Github pull requests should be
+Patches should be submitted as pull requests on https://code.ffmpeg.org.
+Github pull requests should be
avoided because they are not part of our review process and will be ignored.
--
2.49.1
_______________________________________________
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 reply other threads:[~2025-08-07 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 16:33 moshekaplan [this message]
[not found] <20250807163350.3EC6A68D16B@ffbox0-bg.ffmpeg.org>
2025-08-07 16:56 ` Nicolas George
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=20250807163350.6813968D16C@ffbox0-bg.ffmpeg.org \
--to=code@ffmpeg.org \
--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