aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDiego Biurrun <diego@biurrun.de>2008-10-30 10:05:57 +0000
committerDiego Biurrun <diego@biurrun.de>2008-10-30 10:05:57 +0000
commit63d247eadb0b4788749c4220243152ebbfa33d4c (patch)
treee085a33c36b3e36556259e92805d949a32cb9060
parentbc48bb08226777edc443ddc58ed91102682b36f6 (diff)
downloadffmpeg-63d247eadb0b4788749c4220243152ebbfa33d4c.tar.gz
Remove duplicated patch submission checklist entry by putting the more
detailed second entry in place of the first. Originally committed as revision 15749 to svn://svn.ffmpeg.org/ffmpeg/trunk
-rw-r--r--doc/general.texi9
1 files changed, 3 insertions, 6 deletions
diff --git a/doc/general.texi b/doc/general.texi
index 3b4b372155..4ae20a3f2f 100644
--- a/doc/general.texi
+++ b/doc/general.texi
@@ -1045,8 +1045,9 @@ do not attach several unrelated patches to the same mail.
Have you checked that the patch does not introduce buffer overflows or
other security issues?
@item
- If you add a new demuxer or decoder, have you checked that it does not
- crash with damaged input (see tools/trasher)?
+ Did you test your decoder or demuxer against damaged data? If no, see
+ tools/trasher and the noise bitstream filter. Your decoder or demuxer
+ should not crash or end in a (near) infinite loop when fed damaged data.
@item
Is the patch created from the root of the source tree, so it can be
applied with @code{patch -p0}?
@@ -1087,10 +1088,6 @@ do not attach several unrelated patches to the same mail.
improves readability.
@item
Did you provide a suggestion for a clear commit log message?
-@item
- Did you test your decoder or demuxer against damaged data? If no, see
- tools/trasher and the noise bitstream filter. Your decoder or demuxer
- should not crash or end in a (near) infinite loop when fed damaged data.
@end enumerate
@section Patch review process