Most arguments that could be provided to a test have short forms.
Unless documented the only way to learn then is to read the code.

Signed-off-by: Ilya Bobyr <>
 t/README |   10 +++++-----
 1 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/t/README b/t/README
index caeeb9d..ccb5989 100644
--- a/t/README
+++ b/t/README
@@ -71,7 +71,7 @@ You can pass --verbose (or -v), --debug (or -d), and 
 (or -i) command line argument to the test, or by setting GIT_TEST_OPTS
 appropriately before running "make".
        This makes the test more verbose.  Specifically, the
        command being run and their output if any are also
@@ -81,7 +81,7 @@ appropriately before running "make".
        numbers matching <pattern>.  The number matched against is
        simply the running count of the test within the file.
        This may help the person who is developing a new test.
        It causes the command defined with test_debug to run.
        The "trash" directory (used to store all temporary data
@@ -89,18 +89,18 @@ appropriately before running "make".
        failed tests so that you can inspect its contents after
        the test finished.
        This causes the test to immediately exit upon the first
        failed test. Cleanup commands requested with
        test_when_finished are not executed if the test failed,
        in order to keep the state for inspection by the tester
        to diagnose the bug.
        This causes additional long-running tests to be run (where
        available), for more exhaustive testing.
        Execute all Git binaries under valgrind tool <tool> and exit
        with status 126 on errors (just like regular tests, this will
        only stop the test script when running under -i).

To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to
More majordomo info at

Reply via email to