diff options
| author | Michael Niedermayer <michaelni@gmx.at> | 2012-06-29 01:13:16 +0200 |
|---|---|---|
| committer | Michael Niedermayer <michaelni@gmx.at> | 2012-06-29 01:17:07 +0200 |
| commit | c103dc0b48e9d2a9c266d48582bd26f0ff850169 (patch) | |
| tree | 3161971574894ee5e4947168fcc1d865cf76d7d1 /doc/git-howto.texi | |
| parent | 4e82bdea60c86f59482b152446b0e3be43b78fc3 (diff) | |
git-howto: replace confusing and incorrect text about he testsuite by mostly a correct text.
Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
Diffstat (limited to 'doc/git-howto.texi')
| -rw-r--r-- | doc/git-howto.texi | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/doc/git-howto.texi b/doc/git-howto.texi index a76e58e385..56a0cdaf3c 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. |