[FFmpeg-devel] [PR] doc/developer: Add Forgejo as a way to send patches (PR #22285)

[FFmpeg-devel] [PR] doc/developer: Add Forgejo as a way to send patches (PR #22285)

[Jack Lau via ffmpeg-devel]

PR #22285 opened by Jack Lau (JackLau)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/22285
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/22285.patch

Signed-off-by: Jack Lau <jacklau1222gm@gmail.com>


>From 5f081ca7550dc17a95aa6aaadcdf45be6ddbd38a Mon Sep 17 00:00:00 2001
From: Jack Lau <jacklau1222gm@gmail.com>
Date: Thu, 26 Feb 2026 06:49:32 +0800
Subject: [PATCH] doc/developer: Add Forgejo as a way to send patches

Signed-off-by: Jack Lau <jacklau1222gm@gmail.com>
---
 doc/developer.texi | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/doc/developer.texi b/doc/developer.texi
index 10a2de00df..8cf6893d13 100644
--- a/doc/developer.texi
+++ b/doc/developer.texi
@@ -45,6 +45,7 @@ maintained and developed.
 @end itemize
 
 All proposed code changes should be submitted for review to
+@url{https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls, Forgejo} or
 @url{mailto:ffmpeg-devel@@ffmpeg.org, the development mailing list}, as
 described in more detail in the @ref{Submitting patches} chapter. The code
 should comply with the @ref{Development Policy} and follow the @ref{Coding Rules}.
@@ -723,6 +724,7 @@ Also please if you send several patches, send each patch as a separate mail,
 do not attach several unrelated patches to the same mail.
 
 Patches should be posted to the
+@uref{https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls, Forgejo} or
 @uref{https://lists.ffmpeg.org/mailman/listinfo/ffmpeg-devel, ffmpeg-devel}
 mailing list. Use @code{git send-email} when possible since it will properly
 send patches without requiring extra care. If you cannot, then send patches
-- 
2.52.0

_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org