# [PATCH] asciidoc gets confused by two '^' on the same line

1 messages from 2005-09-16 to 2005-09-16. Participants: Horst von Brand.
Thread: https://gitlist.dev/t/1831

## Horst von Brand, 2005-09-16 18:14

Subject: [PATCH] asciidoc gets confused by two '^' on the same line
Message-ID: <200509161814.j8GIE14h016323@inti.inf.utfsm.cl>
URL: https://gitlist.dev/e/200509161814.j8GIE14h016323%40inti.inf.utfsm.cl

```
Uglify Documentation/git-rev-list.txt to get decent output.

Signed-off-by: Horst H. von Brand <vonbrand@inf.utfsm.cl>


---

 Documentation/git-rev-list.txt |    8 +++++---
 1 files changed, 5 insertions(+), 3 deletions(-)

ceb9e143038dcf62311bc3514ae4d2d0f7854aa4
diff --git a/Documentation/git-rev-list.txt b/Documentation/git-rev-list.txt
--- a/Documentation/git-rev-list.txt
+++ b/Documentation/git-rev-list.txt
@@ -32,8 +32,11 @@ I have the commit object 'bar', but not 
 
 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.
@@ -93,4 +96,3 @@ Documentation by David Greaves, Junio C 
 GIT
 ---
 Part of the link:git.html[git] suite
-

```