Documentation: AsciiDoc spells em-dash as double-dashes, not triple
Again, we do not usually process release notes with AsciiDoc, but it is better to be consistent. This incidentally reveals breakages left by an ancient 5e00439f (Documentation: build html for all files in technical and howto, 2012-10-23). The index-format documentation was originally written to be read as straight text without formatting and when the commit forced everything in Documentation/ to go through AsciiDoc, it did not do any adjustment--hence the double-dashes will be seen in the resulting text that is rendered as preformatted fixed-width without converted into em-dashes. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Junio C Hamano committed
Oct 22, 2015 at 13:02 UTC
3b19dba7030f179cf981a8714693f74c07d915a4
6 files changed
+6
-6
Documentation/RelNotes/1.7.7.txt
+1
-1
@@ -84,7 +84,7 @@ Updates since v1.7.6
84
logic used by "git diff" to determine the hunk header.
85
86
* Invoking the low-level "git http-fetch" without "-a" option (which
87
- git itself never did---normal users should not have to worry about
87
+ git itself never did--normal users should not have to worry about
88
this) is now deprecated.
89
90
* The "--decorate" option to "git log" and its family learned to
Documentation/RelNotes/1.9.0.txt
+1
-1
@@ -177,7 +177,7 @@ Performance, Internal Implementation, etc.
177
* The naming convention of the packfiles has been updated; it used to
178
be based on the enumeration of names of the objects that are
179
contained in the pack, but now it also depends on how the packed
180
- result is represented---packing the same set of objects using
180
+ result is represented--packing the same set of objects using
181
different settings (or delta order) would produce a pack with
182
different name.
183
Documentation/git-bisect.txt
+1
-1
@@ -245,7 +245,7 @@ cannot be tested. If the script exits with this code, the current
245
revision will be skipped (see `git bisect skip` above). 125 was chosen
246
as the highest sensible value to use for this purpose, because 126 and 127
247
are used by POSIX shells to signal specific error status (127 is for
248
-command not found, 126 is for command found but not executable---these
248
+command not found, 126 is for command found but not executable--these
249
details do not matter, as they are normal errors in the script, as far as
250
"bisect run" is concerned).
251
Documentation/git-fetch.txt
+1
-1
@@ -71,7 +71,7 @@ This configuration is used in two ways:
71
* When `git fetch` is run without specifying what branches
72
and/or tags to fetch on the command line, e.g. `git fetch origin`
73
or `git fetch`, `remote.<repository>.fetch` values are used as
74
- the refspecs---they specify which refs to fetch and which local refs
74
+ the refspecs--they specify which refs to fetch and which local refs
75
to update. The example above will fetch
76
all branches that exist in the `origin` (i.e. any ref that matches
77
the left-hand side of the value, `refs/heads/*`) and update the
Documentation/git-push.txt
+1
-1
@@ -61,7 +61,7 @@ be named.
61
If `git push [<repository>]` without any `<refspec>` argument is set to
62
update some ref at the destination with `<src>` with
63
`remote.<repository>.push` configuration variable, `:<dst>` part can
64
-be omitted---such a push will update a ref that `<src>` normally updates
64
+be omitted--such a push will update a ref that `<src>` normally updates
65
without any `<refspec>` on the command line. Otherwise, missing
66
`:<dst>` means to update the same ref as the `<src>`.
67
+
Documentation/technical/index-format.txt
+1
-1
@@ -170,7 +170,7 @@ Git index format
170
171
The entries are written out in the top-down, depth-first order. The
172
first entry represents the root level of the repository, followed by the
173
- first subtree---let's call this A---of the root level (with its name
173
+ first subtree--let's call this A--of the root level (with its name
174
relative to the root level), followed by the first subtree of A (with
175
its name relative to A), ...
176