aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorMichael Niedermayer <michael@niedermayer.cc>2016-10-11 03:05:48 +0200
committerMichael Niedermayer <michael@niedermayer.cc>2016-10-11 23:20:56 +0200
commit51f3278089bb5d65d4a1c47cd037d9d706a254f0 (patch)
tree083f181cc1d230e288ed5d63c96770691f58d506 /doc
parent24022402be4cf3311c673b9a9096081e263b91e2 (diff)
downloadffmpeg-51f3278089bb5d65d4a1c47cd037d9d706a254f0.tar.gz
doc/developer: Mention mime type and patchwork in "Submitting patches"
Suggested-by: ronald Reviewed-by: Steven Liu <lingjiujianke@gmail.com> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
Diffstat (limited to 'doc')
-rw-r--r--doc/developer.texi6
1 files changed, 5 insertions, 1 deletions
diff --git a/doc/developer.texi b/doc/developer.texi
index cf809b9255..dbe1f5421f 100644
--- a/doc/developer.texi
+++ b/doc/developer.texi
@@ -464,7 +464,11 @@ Patches should be posted to the
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
as base64-encoded attachments, so your patch is not trashed during
-transmission.
+transmission. Also ensure the correct mime type is used
+(text/x-diff or text/x-patch or at least text/plain) and that only one
+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.
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