summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorMichael Niedermayer <michael@niedermayer.cc>2018-01-01 13:17:18 +0100
committerMichael Niedermayer <michael@niedermayer.cc>2018-01-06 03:14:38 +0100
commitfba00b7465b23d1c96fe01a8298afeda01a5d8eb (patch)
tree6524d890d31f809c41d0a7a9cd5520d9af3a24fd /doc
parentda5b05c8335d2c29355b95257f466211d04ab81d (diff)
downloadffmpeg-fba00b7465b23d1c96fe01a8298afeda01a5d8eb.tar.gz
doc/fate: Document how to upload samples to the fate suite
Suggested-by: Compn Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
Diffstat (limited to 'doc')
-rw-r--r--doc/fate.texi20
1 files changed, 20 insertions, 0 deletions
diff --git a/doc/fate.texi b/doc/fate.texi
index 7a96c25c72..c9c0d3aea9 100644
--- a/doc/fate.texi
+++ b/doc/fate.texi
@@ -147,6 +147,26 @@ process.
The only thing left is to automate the execution of the fate.sh script and
the synchronisation of the samples directory.
+@chapter Uploading new samples to the fate suite
+
+This is for developers who have an account on the fate suite server.
+If you upload new samples, please make sure they are as small as possible,
+space on each client, network bandwidth and so on benefit from smaller test cases.
+Also keep in mind older checkouts use existing sample files, that means in
+practice generally do not replace, remove or overwrite files as it likely would
+break older checkouts or releases.
+
+@example
+#First update your local samples copy:
+rsync -vauL --chmod=Dg+s,Duo+x,ug+rw,o+r,o-w,+X fate-suite.ffmpeg.org:/home/samples/fate-suite/ ~/fate-suite
+
+#Then do a dry run checking what would be uploaded:
+rsync -vanL --no-g --chmod=Dg+s,Duo+x,ug+rw,o+r,o-w,+X ~/fate-suite/ fate-suite.ffmpeg.org:/home/samples/fate-suite
+
+#Upload the files:
+rsync -vaL --no-g --chmod=Dg+s,Duo+x,ug+rw,o+r,o-w,+X ~/fate-suite/ fate-suite.ffmpeg.org:/home/samples/fate-suite
+@end example
+
@chapter FATE makefile targets and variables