git-[short]log.txt: unify quoted standalone --
authorMartin Ågren <martin.agren@gmail.com>
Tue, 17 Apr 2018 19:15:28 +0000 (21:15 +0200)
committerJunio C Hamano <gitster@pobox.com>
Wed, 18 Apr 2018 03:49:26 +0000 (12:49 +0900)
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>
Documentation/git-log.txt
Documentation/git-shortlog.txt
index be2f10b70b35c2435d7b7b530f1c2c9481982fc2..90761f169444c165f0e94ebc3b7731cd8d85d3f0 100644 (file)
@@ -96,7 +96,7 @@ include::line-range-format.txt[]
        Simplification' below for details and other simplification
        modes.
 +
-Paths may need to be prefixed with ``\-- '' to separate them from
+Paths may need to be prefixed with `--` to separate them from
 options or the revision range, when confusion arises.
 
 include::rev-list-options.txt[]
@@ -125,7 +125,7 @@ EXAMPLES
 `git log --since="2 weeks ago" -- gitk`::
 
        Show the changes during the last two weeks to the file 'gitk'.
-       The ``--'' is necessary to avoid confusion with the *branch* named
+       The `--` is necessary to avoid confusion with the *branch* named
        'gitk'
 
 `git log --name-status release..test`::
index 00a22152a22b1d877f8bd75ee5063a0b6d28cbf0..bc80905a8a06b5121e2c33c83844301a8212c28c 100644 (file)
@@ -73,7 +73,7 @@ them.
        Consider only commits that are enough to explain how the files
        that match the specified paths came to be.
 +
-Paths may need to be prefixed with "\-- " to separate them from
+Paths may need to be prefixed with `--` to separate them from
 options or the revision range, when confusion arises.
 
 MAPPING AUTHORS