summaryrefslogtreecommitdiffstats
path: root/git-rev-list.txt
diff options
context:
space:
mode:
authorJunio C Hamano <junio@hera.kernel.org>2006-05-09 00:32:32 +0000
committerJunio C Hamano <junio@hera.kernel.org>2006-05-09 00:32:32 +0000
commitb0ec2db86c94ac9dae0cea5f66ab34143c40ef7c (patch)
treecd94e5cea58f214ac7d7a08649e4400ee5ca61c1 /git-rev-list.txt
parent6d891e69a947d5abd6ecd44db9748716b8c428f5 (diff)
downloadgit-htmldocs-b0ec2db86c94ac9dae0cea5f66ab34143c40ef7c.tar.gz
Autogenerated HTML docs for v1.3.2-g45f7
Diffstat (limited to 'git-rev-list.txt')
-rw-r--r--git-rev-list.txt7
1 files changed, 4 insertions, 3 deletions
diff --git a/git-rev-list.txt b/git-rev-list.txt
index 8255ae1bc..ad6d14c55 100644
--- a/git-rev-list.txt
+++ b/git-rev-list.txt
@@ -68,9 +68,10 @@ OPTIONS
--bisect::
Limit output to the one commit object which is roughly halfway
between the included and excluded commits. Thus, if 'git-rev-list
- --bisect foo ^bar ^baz' outputs 'midpoint', the output
- of 'git-rev-list foo ^midpoint' and 'git-rev-list midpoint
- ^bar ^baz' would be of roughly the same length. Finding the change
+ --bisect foo {caret}bar {caret}baz' outputs 'midpoint', the output
+ of 'git-rev-list foo {caret}midpoint' and 'git-rev-list midpoint
+ {caret}bar {caret}baz' would be of roughly the same length.
+ Finding the change
which introduces a regression is thus reduced to a binary search:
repeatedly generate and test new 'midpoint's until the commit chain
is of length one.