[FFmpeg-cvslog] git-howto: replace confusing and incorrect text about he testsuite by mostly a correct text .

Michael Niedermayer git at videolan.org
Fri Jun 29 01:22:17 CEST 2012


ffmpeg | branch: master | Michael Niedermayer <michaelni at gmx.at> | Fri Jun 29 01:13:16 2012 +0200| [c103dc0b48e9d2a9c266d48582bd26f0ff850169] | committer: Michael Niedermayer

git-howto: replace confusing and incorrect text about he testsuite by mostly a correct text.

Signed-off-by: Michael Niedermayer <michaelni at gmx.at>

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

 doc/git-howto.texi |    7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/doc/git-howto.texi b/doc/git-howto.texi
index a76e58e..56a0cda 100644
--- a/doc/git-howto.texi
+++ b/doc/git-howto.texi
@@ -371,9 +371,10 @@ Next let the code pass through a full run of our testsuite.
 @item if fate fails due to missing samples run @command{make fate-rsync} and retry
 @end itemize
 
-While the test suite covers a wide range of possible problems, it is not
-a panacea. Do not hesitate to perform any other tests necessary to convince
-yourself that the changes you are about to push actually work as expected.
+Make sure all your changes have been checked before pushing them, the
+testsuite only checks against regressions and that only to some extend. It does
+obviously not check newly added features/code to be working unless you have
+added a test for that (which is recommanded btw).
 
 Also note that every single commit should pass the test suite, not just
 the result of a series of patches.



More information about the ffmpeg-cvslog mailing list