git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Documentation: fix graph in git-rev-parse.txt

From
Junio C Hamano <gitster@pobox.com>
Date
May 26, 2008, 23:21 UTC
Message-ID
<7vbq2s4poy.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<200805261524.02355.barra_cuda@katamail.com>
Michele Ballabio <barra_cuda@katamail.com> writes:
Show 12 quoted lines
> 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
Previous: Michele Ballabio
Message 2 of 2 in “Documentation: fix graph in git-rev-parse.txt”
  1. Documentation: fix graph in git-rev-parse.txtMichele Ballabio, May 26, 2008
  2. Junio C HamanoMay 26, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.