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

diff --git a/doc/general.texi b/doc/general.texi
index 3b4b3721559764504779235b8997f27b72d5932b..4ae20a3f2f1f9ecf7582d79e215e8ed669be8668 100644 (file)
--- 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