[FFmpeg-cvslog] doc/developer: add description about safely sending patches via E-Mail clients

[Soft Works]

ffmpeg | branch: master | Soft Works <softworkz at hotmail.com> | Sat Aug  7 20:29:16 2021 +0000| [89ba6e9a04d2852d5d042dfd2afde727d2f39bea] | committer: Marton Balint

doc/developer: add description about safely sending patches via E-Mail clients

Signed-off-by: softworkz <softworkz at hotmail.com>
Signed-off-by: Marton Balint <cus at passwd.hu>

> http://git.videolan.org/gitweb.cgi/ffmpeg.git/?a=commit;h=89ba6e9a04d2852d5d042dfd2afde727d2f39bea
---

 doc/developer.texi | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/doc/developer.texi b/doc/developer.texi
index b33cab0fc7..addee0d826 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.
 
+ at subheading Sending patches from email clients
+Using @code{git send-email} might not be desirable for everyone. The
+following trick allows to send patches via email 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:
+
+ at verbatim
+git format-patch -s -o "outputfolder" --add-header "X-Unsent: 1" --suffix .eml --to ffmpeg-devel at ffmpeg.org -1 1a2b3c4d
+ at end verbatim
+
+Now you'll just need to open the eml file with the email application
+and execute 'Send'.
+
+ at 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