Most arguments that could be provided to a test have short forms.
Unless documented, the only way to learn them is to read the code.
Signed-off-by: Ilya Bobyr <ilya.bo...@gmail.com>
---
Minor changes according to comments in
http://www.mail-archive.com/git@vger.kernel.org/msg46423.html
Ramsay Jones
and
http://www.mail-archive.com/git@vger.kernel.org/msg46512.html
Eric Sunshine
t/README | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/t/README b/t/README
index caeeb9d..6b93aca 100644
--- a/t/README
+++ b/t/README
@@ -71,7 +71,7 @@ You can pass --verbose (or -v), --debug (or -d), and
--immediate
(or -i) command line argument to the test, or by setting GIT_TEST_OPTS
appropriately before running "make".
---verbose::
+-v,--verbose::
This makes the test more verbose. Specifically, the
command being run and their output if any are also
output.
@@ -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.
---debug::
+-d,--debug::
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,14 +89,14 @@ appropriately before running "make".
failed tests so that you can inspect its contents after
the test finished.
---immediate::
+-i,--immediate::
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.
---long-tests::
+-l,--long-tests::
This causes additional long-running tests to be run (where
available), for more exhaustive testing.
--
1.7.9
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
