From: Junio C Hamano <gitster@pobox.com>
To: Michele Ballabio <barra_cuda@katamail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation: fix graph in git-rev-parse.txt
Date: Mon, 26 May 2008 16:21:17 -0700 [thread overview]
Message-ID: <7vbq2s4poy.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <200805261524.02355.barra_cuda@katamail.com> (Michele Ballabio's message of "Mon, 26 May 2008 15:24:02 +0200")
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
prev parent reply other threads:[~2008-05-26 23:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vbq2s4poy.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=barra_cuda@katamail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).