[Ffmpeg-cvslog] r8745 - trunk/doc/ffmpeg-doc.texi
michael
subversion
Tue Apr 17 15:07:31 CEST 2007
Author: michael
Date: Tue Apr 17 15:07:31 2007
New Revision: 8745
Modified:
trunk/doc/ffmpeg-doc.texi
Log:
patch submission checklist
Modified: trunk/doc/ffmpeg-doc.texi
==============================================================================
--- trunk/doc/ffmpeg-doc.texi (original)
+++ trunk/doc/ffmpeg-doc.texi Tue Apr 17 15:07:31 2007
@@ -1623,6 +1623,53 @@ and has no lrint()')
Also please if you send several patches, send each patch as seperate mail,
dont attach several unrelated patches to the same mail.
+ at section patch submission checklist
+
+ at enumerate
+ at item
+ Do the regression tests pass with the patch applied?
+ at item
+ Is the patch a unified diff?
+ at item
+ Is the patch against latest ffmpeg SVN?
+ at item
+ Are you subscribed to ffmpeg-dev?
+ (the list is subscribers only due to spam)
+ at item
+ Have you checked that the changes are minimal, so that the same cannot be
+ achived with a smaller patch and/or simpler final code?
+ at item
+ If the change is to speed critical code did you benchmark it?
+ at item
+ Have you checked that the patch does not intruduce buffer overflows or
+ other security issues?
+ at item
+ Is the patch made from the root of the source, so it can be applied with -p0?
+ at item
+ Does the patch not mix functional and cosmetic changes?
+ at item
+ Is the patch attached to the email you send?
+ at item
+ Is the mime type of the patch correct? (not application/octet-stream)
+ at item
+ If the patch fixes a bug did you provide a verbose analysis of the bug?
+ at item
+ If the patch fixes a bug did you provide enough information including
+ a sample, so the bug can be reproduced and the fix can be verified?
+ at item
+ Did you provide a verbose summary about what the patch does change?
+ at item
+ Did you provide a verbose explanation why it changes things like it does?
+ at item
+ Did you provide a verbose summary of the user vissible advantages and
+ disadvantages if the patch is applied?
+ at item
+ Did you provide an example so we can verify the new feature added by the
+ patch easily?
+ at item
+ If you did any benchmarks, did you provide them in the mail?
+ at end enumerate
+
@section Patch review process
All patches posted to ffmpeg-devel will be reviewed, unless they contain a
More information about the ffmpeg-cvslog
mailing list