mirror of
https://github.com/git/git.git
synced 2024-10-29 21:37:53 +01:00
[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>
This commit is contained in:
parent
b93aa3ec95
commit
ed0a84883e
1 changed files with 5 additions and 2 deletions
|
@ -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
|
The *--bisect* flag limits output to the one commit object which is
|
||||||
roughly halfway between the included and excluded commits. Thus,
|
roughly halfway between the included and excluded commits. Thus,
|
||||||
if 'git-rev-list --bisect foo ^bar ^baz' outputs 'midpoint', the output
|
if 'git-rev-list --bisect foo ^bar
|
||||||
of 'git-rev-list foo ^midpoint' and 'git-rev-list midpoint ^bar ^baz'
|
^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
|
would be of roughly the same length. Finding the change which introduces
|
||||||
a regression is thus reduced to a binary search: repeatedly generate and
|
a regression is thus reduced to a binary search: repeatedly generate and
|
||||||
test new 'midpoint's until the commit chain is of length one.
|
test new 'midpoint's until the commit chain is of length one.
|
||||||
|
|
Loading…
Reference in a new issue