summaryrefslogtreecommitdiffstats
path: root/git-bisect.txt
diff options
context:
space:
mode:
authorJunio C Hamano <junio@hera.kernel.org>2008-11-10 00:08:57 +0000
committerJunio C Hamano <junio@hera.kernel.org>2008-11-10 00:08:57 +0000
commit175a1bdd87499aaaceb7c4a49a872797117ab16c (patch)
tree04a13f37f09a4ff816fb78b5cd52a6572815514a /git-bisect.txt
parent08e02ae51d6a089e948282d7e69ca090f1a8dabd (diff)
downloadgit-htmldocs-175a1bdd87499aaaceb7c4a49a872797117ab16c.tar.gz
Autogenerated HTML docs for v1.6.0.4-608-ga9645
Diffstat (limited to 'git-bisect.txt')
-rw-r--r--git-bisect.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/git-bisect.txt b/git-bisect.txt
index c7981efcd..39034ec7d 100644
--- a/git-bisect.txt
+++ b/git-bisect.txt
@@ -26,7 +26,7 @@ on the subcommand:
git bisect log
git bisect run <cmd>...
-This command uses 'git-rev-list --bisect' to help drive the
+This command uses 'git rev-list --bisect' to help drive the
binary search process to find which change introduced a bug, given an
old "good" commit object name and a later "bad" commit object name.
@@ -101,7 +101,7 @@ $ git bisect visualize
to see the currently remaining suspects in 'gitk'. `visualize` is a bit
too long to type and `view` is provided as a synonym.
-If 'DISPLAY' environment variable is not set, 'git-log' is used
+If 'DISPLAY' environment variable is not set, 'git log' is used
instead. You can even give command line options such as `-p` and
`--stat`.
@@ -215,7 +215,7 @@ tweaks (e.g., s/#define DEBUG 0/#define DEBUG 1/ in a header file, or
work around other problem this bisection is not interested in")
applied to the revision being tested.
-To cope with such a situation, after the inner 'git-bisect' finds the
+To cope with such a situation, after the inner 'git bisect' finds the
next revision to test, with the "run" script, you can apply that tweak
before compiling, run the real test, and after the test decides if the
revision (possibly with the needed tweaks) passed the test, rewind the