diff mbox series

[FFmpeg-devel,v3] doc/developer: Add description about safely sending patches via E-Mail clients

Message ID MN2PR04MB59812653DFFD8FCCAA31DBC6BAF49@MN2PR04MB5981.namprd04.prod.outlook.com
State New
Headers show
Series [FFmpeg-devel,v3] doc/developer: Add description about safely sending patches via E-Mail clients
Related show

Checks

Context Check Description
andriy/x86_make success Make finished
andriy/x86_make_fate success Make fate finished
andriy/PPC64_make success Make finished
andriy/PPC64_make_fate success Make fate finished

Commit Message

Soft Works Aug. 7, 2021, 8:29 p.m. UTC
Signed-off-by: softworkz <softworkz@hotmail.com>
---
v3: fixed typo
 doc/developer.texi | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)
diff mbox series

Patch

diff --git a/doc/developer.texi b/doc/developer.texi
index b33cab0fc7..86f63c49b3 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 execute '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