From 8bff1d7cb092b01f04285ff63be368dccbd973a3 Mon Sep 17 00:00:00 2001 From: Michael Niedermayer Date: Fri, 29 Jun 2012 00:33:49 +0200 Subject: [PATCH] git-howto: remove inconvenient and odd 24h limit on rsync This was never true for FFmpeg in this form. Signed-off-by: Michael Niedermayer --- doc/git-howto.texi | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/doc/git-howto.texi b/doc/git-howto.texi index d01f21b6ad..68da93a39d 100644 --- a/doc/git-howto.texi +++ b/doc/git-howto.texi @@ -373,16 +373,13 @@ to ensure no local changes still need to be committed and that no local changes may have thrown off the results of your testing. @end itemize -Next let the code pass through a full run of our testsuite. Before you do, -the command @command{make fate-rsync} will update the test samples. Changes -to the samples set are not very common and commits depending on samples -changes are delayed for at least 24 hours to allow the new samples to -propagate, so updating it once per day is sufficient. Now execute +Next let the code pass through a full run of our testsuite. @itemize @item @command{make distclean} @item @command{/path/to/ffmpeg/configure} @item @command{make check} +@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