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

[PATCH] doc: correct command formatting

From
Adam Dinwoodie <adam@dinwoodie.org>
Date
Sep 28, 2017, 14:06 UTC
Message-ID
<20170928140648.GC9439@dinwoodie.org>

Leaving spaces around the `-delimeters for commands means asciidoc fails to parse them as the start of a literal string. Remove an extraneous space that is causing a literal to not be formatted as such.

Signed-off-by: Adam Dinwoodie <adam@dinwoodie.org>
---
 Documentation/git.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/git.txt b/Documentation/git.txt
index 6e3a6767e..98b9b46b9 100644
--- a/Documentation/git.txt
+++ b/Documentation/git.txt
@@ -75,7 +75,7 @@ example the following invocations are equivalent:
 Note that omitting the `=` in `git -c foo.bar ...` is allowed and sets
 `foo.bar` to the boolean true value (just like `[foo]bar` would in a
 config file). Including the equals but with an empty value (like `git -c
-foo.bar= ...`) sets `foo.bar` to the empty string which ` git config
+foo.bar= ...`) sets `foo.bar` to the empty string which `git config
 --bool` will convert to `false`.
 
 --exec-path[=<path>]::
-- 
2.14.1
Next: Andreas Heiduk
Message 1 of 8 in “doc: correct command formatting”
  1. doc: correct command formattingAdam Dinwoodie, Sep 28, 2017
  2. Andreas HeidukSep 28, 2017
  3. Jonathan NiederSep 28, 2017
  4. Andreas HeidukSep 28, 2017
  5. Junio C HamanoSep 29, 2017
  6. Jonathan NiederSep 29, 2017
  7. Junio C HamanoSep 29, 2017
  8. Jonathan NiederSep 28, 2017

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.