Andrew's git
/
gitweb.git
/ diff
summary
|
log
|
commit
| diff |
tree
commit
grep
author
committer
pickaxe
?
re
[PATCH] Documentation/git-rev-list.txt typo fix
author
jdl@freescale.com
<jdl@freescale.com>
Thu, 15 Sep 2005 22:40:13 +0000
(17:40 -0500)
committer
Junio C Hamano
<junkio@cox.net>
Fri, 16 Sep 2005 00:06:58 +0000
(17:06 -0700)
Fix the "superscript" problem on the git-rev-list doc page.
Signed-off-by: Jon Loeliger <jdl@freescale.com>
Signed-off-by: Junio C Hamano <junkio@cox.net>
Documentation/git-rev-list.txt
patch
|
blob
|
history
raw
|
patch
|
inline
| side by side (parent:
5bdbaaa
)
diff --git
a/Documentation/git-rev-list.txt
b/Documentation/git-rev-list.txt
index 35fecf3f831a55cb1616f72198a77d9fe1bf617d..8bf5d6124314005eb4b6ab61d7ba42d0e30fa73d 100644
(file)
--- a/
Documentation/git-rev-list.txt
+++ b/
Documentation/git-rev-list.txt
@@
-32,8
+32,8
@@
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,
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.
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.