[FFmpeg-cvslog] doc/developer: Mention mime type and patchwork in "Submitting patches"

Michael Niedermayer git at videolan.org
Wed Oct 12 00:25:14 EEST 2016

ffmpeg | branch: master | Michael Niedermayer <michael at niedermayer.cc> | Tue Oct 11 03:05:48 2016 +0200| [51f3278089bb5d65d4a1c47cd037d9d706a254f0] | committer: Michael Niedermayer

doc/developer: Mention mime type and patchwork in "Submitting patches"

Suggested-by: ronald
Reviewed-by: Steven Liu <lingjiujianke at gmail.com>
Signed-off-by: Michael Niedermayer <michael at niedermayer.cc>

> http://git.videolan.org/gitweb.cgi/ffmpeg.git/?a=commit;h=51f3278089bb5d65d4a1c47cd037d9d706a254f0

 doc/developer.texi | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/doc/developer.texi b/doc/developer.texi
index cf809b9..dbe1f54 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. 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

More information about the ffmpeg-cvslog mailing list