Documentation: bisect: change a few instances of "git-cmd" to "git cmd"
Signed-off-by: Christian Couder <chriscool@tuxfamily.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Christian Couder committed
Nov 9, 2008 at 14:53 UTC
5bcce8494a2ee09250404b8b086cbd62f9506703
1 file changed
+3
-3
Documentation/git-bisect.txt
+3
-3
@@ -26,7 +26,7 @@ on the subcommand:
26
git bisect log
27
git bisect run <cmd>...
28
29
-This command uses 'git-rev-list --bisect' to help drive the
29
+This command uses 'git rev-list --bisect' to help drive the
30
binary search process to find which change introduced a bug, given an
31
old "good" commit object name and a later "bad" commit object name.
32
@@ -101,7 +101,7 @@ $ git bisect visualize
101
to see the currently remaining suspects in 'gitk'. `visualize` is a bit
102
too long to type and `view` is provided as a synonym.
103
104
-If 'DISPLAY' environment variable is not set, 'git-log' is used
104
+If 'DISPLAY' environment variable is not set, 'git log' is used
105
instead. You can even give command line options such as `-p` and
106
`--stat`.
107
@@ -215,7 +215,7 @@ tweaks (e.g., s/#define DEBUG 0/#define DEBUG 1/ in a header file, or
215
work around other problem this bisection is not interested in")
216
applied to the revision being tested.
217
218
-To cope with such a situation, after the inner 'git-bisect' finds the
218
+To cope with such a situation, after the inner 'git bisect' finds the
219
next revision to test, with the "run" script, you can apply that tweak
220
before compiling, run the real test, and after the test decides if the
221
revision (possibly with the needed tweaks) passed the test, rewind the