summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 5bdbaaa)
raw | patch | inline | side by side (parent: 5bdbaaa)
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>
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 |
index 35fecf3f831a55cb1616f72198a77d9fe1bf617d..8bf5d6124314005eb4b6ab61d7ba42d0e30fa73d 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.