diff options
author | Owen W. Taylor <otaylor@fishsoup.net> | 2012-03-01 11:48:17 -0500 |
---|---|---|
committer | Owen W. Taylor <otaylor@fishsoup.net> | 2012-03-01 11:57:18 -0500 |
commit | f0e8b5c7233882f948a2638ae2711862477692fa (patch) | |
tree | d88bcd3006c6bb4cbdda036b17e2cd61708f9aa8 | |
parent | 89806cf16cb17765f1e63ac132c13eed4c3a42ac (diff) | |
download | git-bz-f0e8b5c7233882f948a2638ae2711862477692fa.tar.gz |
Work around line-break problems
The two lines for the different versions of 'git bz edit' are treated
by asciidoc as a single paragraph and line-wrapped.
In theory, a + at the end of a line is a forced line-break with
asciidoc, but in the manpage generation route, this doesn't work
properly - the magic in a2x that is supposed to turn the asciidoc-br
processing instruction into a line break doesn't work. (We aren't
using a2x at the moment for the conversion, but no real reason to
switch if it doesn't work better.)
So, use a [verse] paragraph instead. This results in mis-indentation,
but slightly better than the previous breakage.
https://bugzilla.gnome.org/show_bug.cgi?id=670686
-rw-r--r-- | git-bz.txt | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -192,6 +192,7 @@ default product if none is given on the command line). edit ~~~~ +[verse] 'git bz edit' (<bug reference> | <commit> | <revision range>) 'git bz edit' --pushed (<commit> | <revision range>) |