From 9e0c3508d0d4b453e5e24841b0c73fe520f957a1 Mon Sep 17 00:00:00 2001 From: diego Date: Thu, 30 Oct 2008 10:05:57 +0000 Subject: [PATCH] Remove duplicated patch submission checklist entry by putting the more detailed second entry in place of the first. git-svn-id: file:///var/local/repositories/ffmpeg/trunk@15749 9553f0bf-9b14-0410-a0b8-cfaf0461ba5b --- doc/general.texi | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/doc/general.texi b/doc/general.texi index 3b4b37215..4ae20a3f2 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 -- 2.39.2