summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Hagervall <hager@cs.umu.se>2005-09-16 14:24:12 (GMT)
committerJunio C Hamano <junkio@cox.net>2005-09-16 22:16:35 (GMT)
commited0a84883ec33cd2d4ee7f66204de7dab13353d8 (patch)
tree0e4f28b597cb3be28e5f32569bc6d2105b9918eb
parentb93aa3ec9506618e9a22c04d775b35f31e7e068f (diff)
downloadgit-ed0a84883ec33cd2d4ee7f66204de7dab13353d8.zip
git-ed0a84883ec33cd2d4ee7f66204de7dab13353d8.tar.gz
git-ed0a84883ec33cd2d4ee7f66204de7dab13353d8.tar.bz2
[PATCH] PATCH Documentation/git-rev-list.txt typo fix
An earlier commit causes a mismatch in <emphasis> and <superscript> tags, one way of fixing it is having no more than one caret symbol per line, which is the only solution I found in the asciidoc documentation. Ugly, but it works. [jc: ugly indeed but that is not Peter's fault.] Signed-off-by: Peter Hagervall <hager@cs.umu.se> Signed-off-by: Junio C Hamano <junkio@cox.net>
-rw-r--r--Documentation/git-rev-list.txt7
1 files changed, 5 insertions, 2 deletions
diff --git a/Documentation/git-rev-list.txt b/Documentation/git-rev-list.txt
index 8bf5d61..32c06a1 100644
--- a/Documentation/git-rev-list.txt
+++ b/Documentation/git-rev-list.txt
@@ -32,8 +32,11 @@ I have the commit object 'bar', but not 'foo'".
The *--bisect* flag limits 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'
+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 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.