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

[PATCH v2] Documentation: fmt-merge-msg: fix markup in example

From
SCStefan Christ <contact@stefanchrist.eu>
Date
Oct 28, 2016, 15:07 UTC
Message-ID
<1477667244-17887-1-git-send-email-contact@stefanchrist.eu>
In-Reply-To
<alpine.LFD.2.20.1610280623400.524@localhost.localdomain>
The example was not rendered as verbatim text. Fix it.
Signed-off-by: Stefan Christ <contact@stefanchrist.eu>
---
v2: fix misspelling in subject
Hi,

thanks to rday for spotting the typo in the subject line (I missed to autoenable the spell checking in vim) and thanks to Peff for the asciidoc explanation.

Kind regards,
	Stefan Christ
---
 Documentation/git-fmt-merge-msg.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-fmt-merge-msg.txt b/Documentation/git-fmt-merge-msg.txt
index 6526b17..44892c4 100644
--- a/Documentation/git-fmt-merge-msg.txt
+++ b/Documentation/git-fmt-merge-msg.txt
@@ -60,10 +60,10 @@ merge.summary::
 EXAMPLE
 -------
 
---
+---------
 $ git fetch origin master
 $ git fmt-merge-msg --log <$GIT_DIR/FETCH_HEAD
---
+---------
 
 Print a log message describing a merge of the "master" branch from
 the "origin" remote.
-- 
2.7.3
Previous: Robert P. J. DayNext: Jeff King
Message 3 of 6 in “Documenation: fmt-merge-msg: fix markup in example”
  1. Documenation: fmt-merge-msg: fix markup in exampleStefan Christ, Oct 28, 2016
  2. Robert P. J. DayOct 28, 2016
  3. Documentation: fmt-merge-msg: fix markup in exampleStefan Christ, Oct 28, 2016
  4. Jeff KingOct 28, 2016
  5. Junio C HamanoOct 28, 2016
  6. Stefan ChristOct 28, 2016

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.