flacdec: fix memleaks

[ffmpeg] / doc / fate.texi

diff --git a/doc/fate.texi b/doc/fate.texi
index 688c6421f84ca11e425e444b56973ad95c8c5f23..e04f62fc798d084b6555e9fbab14ae6f72773ccf 100644 (file)
--- a/doc/fate.texi
+++ b/doc/fate.texi
@@ -85,7 +85,7 @@ To use a custom wrapper to run the test, pass @option{--target-exec} to
 @chapter Submitting the results to the FFmpeg result aggregation server
 
   To submit your results to the server you should run fate through the
-shell script tests/fate.sh from the FFmpeg sources. This script needs
+shell script @file{tests/fate.sh} from the FFmpeg sources. This script needs
 to be invoked with a configuration file as its first argument.
 
 @example
@@ -121,8 +121,9 @@ present in $workdir as specified in the configuration file:
     @item version
 @end itemize
 
-  When you have everything working properly you can create an SSH key and
-send its public part to the FATE server administrator.
+  When you have everything working properly you can create an SSH key pair
+and send the public key to the FATE server administrator who can be contacted
+at the email address @email{fate-admin@@ffmpeg.org}.
 
   Configure your SSH client to use public key authentication with that key
 when connecting to the FATE server. Also do not forget to check the identity
@@ -132,6 +133,11 @@ The FATE server's fingerprint is:
 
   b1:31:c8:79:3f:04:1d:f8:f2:23:26:5a:fd:55:fa:92
 
+  If you have problems connecting to the FATE server, it may help to try out
+the @command{ssh} command with one or more @option{-v} options. You should
+get detailed output concerning your SSH configuration and the authentication
+process.
+
   The only thing left is to automate the execution of the fate.sh script and
 the synchronisation of the samples directory.
 
@@ -181,7 +187,8 @@ the synchronisation of the samples directory.
     through @command{ssh}.
 @end table
 
-Example:
+@section Examples
+
 @example
 make V=1 SAMPLES=/var/fate/samples THREADS=2 CPUFLAGS=mmx fate
 @end example