diff options
| author | Soft Works <softworkz@hotmail.com> | 2021-08-07 20:29:16 +0000 |
|---|---|---|
| committer | Marton Balint <cus@passwd.hu> | 2021-11-13 19:55:20 +0100 |
| commit | 89ba6e9a04d2852d5d042dfd2afde727d2f39bea (patch) | |
| tree | 0d6171a54902d02f7615db7dddcb25c34f516563 | |
| parent | fba4d6f72b27b0dce1774e8e1eee2245cad9ffd2 (diff) | |
doc/developer: add description about safely sending patches via E-Mail clients
Signed-off-by: softworkz <softworkz@hotmail.com>
Signed-off-by: Marton Balint <cus@passwd.hu>
| -rw-r--r-- | doc/developer.texi | 16 |
1 files changed, 16 insertions, 0 deletions
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. +@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: + +@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 email 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 |