Am 28.09.2017 um 16:06 schrieb Adam Dinwoodie:
> 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 <[email protected]>
> ---
> 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>]::
>
+1, Thanks for spotting.
I did a quick
grep -r " ` "
which came up with with another relevant place:
Documentation/git-format-patch.txt: `--subject-prefix` option) has ` v<n>`
appended to it. E.g.
But here the space IS relevant but asciidoc does not pick up
the formatting. Perhaps that one could read like this:
`--subject-prefix` option) has `<SPACE>v<n>` appended to it. E.g.
