t/README: --valgrind already implies -v
This was missed in 3da9365 (Tests: let --valgrind imply --verbose and --tee, 2009-02-04). Signed-off-by: Thomas Rast <trast@inf.ethz.ch> Acked-by: Johannes Schindelin <Johannes.Schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Thomas Rast committed
Mar 31, 2013 at 10:00 UTC
fd4fab894f564d04e0e3fb60659e6babfc4e3d81
1 file changed
+1
-2
t/README
+1
-2
@@ -95,8 +95,7 @@ appropriately before running "make".
95
--valgrind::
96
Execute all Git binaries with valgrind and exit with status
97
126 on errors (just like regular tests, this will only stop
98
- the test script when running under -i). Valgrind errors
99
- go to stderr, so you might want to pass the -v option, too.
98
+ the test script when running under -i).
99
100
Since it makes no sense to run the tests with --valgrind and
101
not see any output, this option implies --verbose. For