git-[short]log.txt: unify quoted standalone --

In git-log.txt, we have an instance of \--, which is known to sometimes render badly. This one is even worse than normal though, since ``\-- '' (with or without that trailing space) appears to be entirely broken, both in HTML and manpages, both with AsciiDoc (version 8.6.9) and Asciidoctor (version 1.5.4). Further down in git-log.txt we have a ``--'', which renders good. In git-shortlog.txt, we use "\-- " (including the quotes and the space), which happens to look fairly good. I failed to find any other similar instances. So all in all, we quote a double-dash in three different places and do it differently each time, with various degrees of success. Switch all of these to `--`. This sets the double-dash in monospace and matches what we usually do with example command line usages and options. Note that we drop the trailing space as well, since `-- ` does not render well. These should still be clear enough since just a few lines above each instance, the space is clearly visible in a longer context. Signed-off-by: Martin Ågren <martin.agren@gmail.com>

Martin Ågren committed Apr 17, 2018 at 21:15 UTC 6955047ff48c7f2a29889d5372414756f2723049
2 files changed +3 -3
Documentation/git-log.txt
+2 -2
@@ -96,7 +96,7 @@ include::line-range-format.txt[]
96 Simplification' below for details and other simplification
97 modes.
98 +
99 -Paths may need to be prefixed with ``\-- '' to separate them from
99 +Paths may need to be prefixed with `--` to separate them from
100 options or the revision range, when confusion arises.
101
102 include::rev-list-options.txt[]
@@ -125,7 +125,7 @@ EXAMPLES
125 `git log --since="2 weeks ago" -- gitk`::
126
127 Show the changes during the last two weeks to the file 'gitk'.
128 - The ``--'' is necessary to avoid confusion with the *branch* named
128 + The `--` is necessary to avoid confusion with the *branch* named
129 'gitk'
130
131 `git log --name-status release..test`::
Documentation/git-shortlog.txt
+1 -1
@@ -73,7 +73,7 @@ them.
73 Consider only commits that are enough to explain how the files
74 that match the specified paths came to be.
75 +
76 -Paths may need to be prefixed with "\-- " to separate them from
76 +Paths may need to be prefixed with `--` to separate them from
77 options or the revision range, when confusion arises.
78
79 MAPPING AUTHORS