(v2: fix doc build)
Signed-off-by: softworkz <softwo...@hotmail.com>
---
doc/developer.texi | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/doc/developer.texi b/doc/developer.texi
index b33cab0fc7..ce5500b85d 100644
--- a/doc/developer.texi
+++ b/doc/developer.texi
@@ -494,6 +494,22 @@ patch is inline or attached per mail.
You can check @url{https://patchwork.ffmpeg.org}, if your patch does not show
up, its mime type
likely was wrong.
+@subheading Sending E-Mail Client - Example for MS Outlook.
+Using @code{git send-email} might not be desirable for everyone. The
+following trick allows to send patches via E-Mail clients in a safe
+way. It has been tested with Outlook and Thunderbird (with X-Unsent
+extension) and might work with other applications.
+
+Create your patch like this:
+
+@verbatim
+git format-patch -s -o "outputfolder" --add-header "X-Unsent: 1" --suffix .eml
--to ffmpeg-devel@ffmpeg.org -1 1a2b3c4d
+@end verbatim
+
+Now you'll just need to open the eml file with the E-Mail application
+and execure 'Send'.
+
+@subheading Reviews.
Your patch will be reviewed on the mailing list. You will likely be asked
to make some changes and are expected to send in an improved version that
incorporates the requests from the review. This process may go through
--
2.28.0.windows.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-requ...@ffmpeg.org with subject "unsubscribe".
