doc: correct command formatting
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> Acked-by: Andreas Heiduk <asheiduk@gmail.com> Reviewed-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Adam Dinwoodie committed
Sep 28, 2017 at 15:06 UTC
5e633326e452a26c418fd86bb49f0baf236ff172
1 file changed
+1
-1
Documentation/git.txt
+1
-1
@@ -75,7 +75,7 @@ example the following invocations are equivalent:
75
Note that omitting the `=` in `git -c foo.bar ...` is allowed and sets
76
`foo.bar` to the boolean true value (just like `[foo]bar` would in a
77
config file). Including the equals but with an empty value (like `git -c
78
-foo.bar= ...`) sets `foo.bar` to the empty string which ` git config
78
+foo.bar= ...`) sets `foo.bar` to the empty string which `git config
79
--bool` will convert to `false`.
80
81
--exec-path[=<path>]::