if it spans multiple files. This makes reviewing your patches much easier
for us and greatly increases your chances of getting your patch applied.
-Use the patcheck tool of ffmpeg to check your patch.
-The tool is located in the tool directory.
+Use the patcheck tool of FFmpeg to check your patch.
+The tool is located in the tools directory.
Run the regression tests before submitting a patch so that you can
verify that there are no big problems.
Remember to do this even if you're just adding a format to a file that is
already being compiled by some other rule, like a raw demuxer.
@item
- Did you add an entry to the table of supported formats or codecs in the
- documentation?
+ Did you add an entry to the table of supported formats or codecs in
+ @file{doc/general.texi}?
@item
Did you add an entry in the Changelog?
@item
audio stream. These are then encoded and decoded with all codecs or
formats. The CRC (or MD5) of each generated file is recorded in a
result file. A 'diff' is launched to compare the reference results and
-the result file.
+the result file. The output is checked immediately after each test
+has run.
The regression tests then go on to test the FFserver code with a
limited set of streams. It is important that this step runs correctly
as well.
-Run 'make test' to test all the codecs and formats.
+Run 'make test' to test all the codecs and formats. Commands like
+'make regtest-mpeg2' can be used to run a single test. By default,
+make will abort if any test fails. To run all tests regardless,
+use make -k. To get a more verbose output, use 'make V=1 test' or
+'make V=2 test'.
Run 'make fulltest' to test all the codecs, formats and FFserver.