* [PATCH] Documentation: fix graph in git-rev-parse.txt
@ 2008-05-26 13:24 Michele Ballabio
2008-05-26 23:21 ` Junio C Hamano
0 siblings, 1 reply; 2+ messages in thread
From: Michele Ballabio @ 2008-05-26 13:24 UTC (permalink / raw)
To: git
Preformatted html and man pages show a mangled graph, caused by a
backslash.
Commit f1ec6b22a8c1ab1cca0f1875f85aea5d2434e5a6 fixed this same issue,
but it seems that new versions of the Asciidoc toolchain changed their
behaviour.
Signed-off-by: Michele Ballabio <barra_cuda@katamail.com>
---
This should fix the problem, but I can't test it because I have an old
Asciidoc installation (works either way here).
Documentation/git-rev-parse.txt | 4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/Documentation/git-rev-parse.txt b/Documentation/git-rev-parse.txt
index 69599ff..82dab73 100644
--- a/Documentation/git-rev-parse.txt
+++ b/Documentation/git-rev-parse.txt
@@ -243,16 +243,18 @@ Here is an illustration, by Jon Loeliger. Both commit nodes B
and C are parents of commit node A. Parent commits are ordered
left-to-right.
+........................................
G H I J
\ / \ /
D E F
- \ | / \
+ \ | / \
\ | / |
\|/ |
B C
\ /
\ /
A
+........................................
A = = A^0
B = A^ = A^1 = A~1
--
1.5.5.1
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] Documentation: fix graph in git-rev-parse.txt
2008-05-26 13:24 [PATCH] Documentation: fix graph in git-rev-parse.txt Michele Ballabio
@ 2008-05-26 23:21 ` Junio C Hamano
0 siblings, 0 replies; 2+ messages in thread
From: Junio C Hamano @ 2008-05-26 23:21 UTC (permalink / raw)
To: Michele Ballabio; +Cc: git
Michele Ballabio <barra_cuda@katamail.com> writes:
> Preformatted html and man pages show a mangled graph, caused by a
> backslash.
>
> Commit f1ec6b22a8c1ab1cca0f1875f85aea5d2434e5a6 fixed this same issue,
> but it seems that new versions of the Asciidoc toolchain changed their
> behaviour.
>
> Signed-off-by: Michele Ballabio <barra_cuda@katamail.com>
> ---
>
> This should fix the problem, but I can't test it because I have an old
> Asciidoc installation (works either way here).
Thanks. I think you also should de-dent the whole picture to keep the
same output, like this...
Documentation/git-rev-parse.txt | 22 ++++++++++++----------
1 files changed, 12 insertions(+), 10 deletions(-)
diff --git a/Documentation/git-rev-parse.txt b/Documentation/git-rev-parse.txt
index 6513c2e..5981c79 100644
--- a/Documentation/git-rev-parse.txt
+++ b/Documentation/git-rev-parse.txt
@@ -238,16 +238,18 @@ Here is an illustration, by Jon Loeliger. Both commit nodes B
and C are parents of commit node A. Parent commits are ordered
left-to-right.
- G H I J
- \ / \ /
- D E F
- \ | / \
- \ | / |
- \|/ |
- B C
- \ /
- \ /
- A
+........................................
+G H I J
+ \ / \ /
+ D E F
+ \ | / \
+ \ | / |
+ \|/ |
+ B C
+ \ /
+ \ /
+ A
+........................................
A = = A^0
B = A^ = A^1 = A~1
^ permalink raw reply related [flat|nested] 2+ messages in thread
end of thread, other threads:[~2008-05-26 23:22 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-05-26 13:24 [PATCH] Documentation: fix graph in git-rev-parse.txt Michele Ballabio
2008-05-26 23:21 ` Junio C Hamano
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).