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

[PATCH] Documentation/git-merge.txt: fix formatting of example block

From
Andreas Schwab <schwab@linux-m68k.org>
Date
Sep 5, 2013, 15:12 UTC
Message-ID
<87sixjb8uq.fsf@igel.home>

You need at least four dashes in a line to have it recognized as listing block delimiter by asciidoc.

Signed-off-by: Andreas Schwab <schwab@linux-m68k.org>
---
 Documentation/git-merge.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-merge.txt b/Documentation/git-merge.txt
index 8c7f2f6..a74c371 100644
--- a/Documentation/git-merge.txt
+++ b/Documentation/git-merge.txt
@@ -186,11 +186,11 @@ In such a case, you can "unwrap" the tag yourself before feeding it
 to `git merge`, or pass `--ff-only` when you do not have any work on
 your own. e.g.
 
----
+----
 git fetch origin
 git merge v1.2.3^0
 git merge --ff-only v1.2.3
----
+----
 
 
 HOW CONFLICTS ARE PRESENTED
-- 
1.8.4

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
Next: Junio C Hamano
Message 1 of 2 in “Documentation/git-merge.txt: fix formatting of example block”
  1. Documentation/git-merge.txt: fix formatting of example blockAndreas Schwab, Sep 5, 2013
  2. Junio C HamanoSep 5, 2013

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.