diff options
| author | jdl@freescale.com <jdl@freescale.com> | 2005-09-16 02:40:13 +0400 |
|---|---|---|
| committer | Junio C Hamano <junkio@cox.net> | 2005-09-16 04:06:58 +0400 |
| commit | 316eee8fe0282a6f14441b0045a32871bdf90d36 (patch) | |
| tree | f4fdd36ea4fe8a92b430c657540ef552a491615e /Documentation | |
| parent | 5bdbaaa4e9dd901dd2907b53bbecfdf3eac9276b (diff) | |
[PATCH] Documentation/git-rev-list.txt typo fix
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>
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/git-rev-list.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/git-rev-list.txt b/Documentation/git-rev-list.txt index 35fecf3f83..8bf5d61243 100644 --- 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, -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. |