summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: b93aa3e)
raw | patch | inline | side by side (parent: b93aa3e)
author | Peter Hagervall <hager@cs.umu.se> | |
Fri, 16 Sep 2005 14:24:12 +0000 (16:24 +0200) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Fri, 16 Sep 2005 22:16:35 +0000 (15:16 -0700) |
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>
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>
Documentation/git-rev-list.txt | patch | blob | history |
index 8bf5d6124314005eb4b6ab61d7ba42d0e30fa73d..32c06a1662319a8c1a1d322a5a9faf54670aeb37 100644 (file)
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.