doc: use "`<literal>`"-style quoting for literal strings
"'<string>'"-style quoting is not appropriate when quoting literal strings in the "Documentation/" subtree. In preparation for adding additional information to this section of git-for-each-ref(1)'s documentation, update them to use "`<literal>`" instead. Signed-off-by: Taylor Blau <me@ttaylorr.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Taylor Blau committed
Oct 1, 2017 at 09:18 UTC
ced1f08b7b0b625a3ce21185573c80e7ada1e3fa
1 file changed
+3
-3
Documentation/git-for-each-ref.txt
+3
-3
@@ -213,12 +213,12 @@ and `date` to extract the named component.
213
The complete message in a commit and tag object is `contents`.
214
Its first line is `contents:subject`, where subject is the concatenation
215
of all lines of the commit message up to the first blank line. The next
216
-line is 'contents:body', where body is all of the lines after the first
216
+line is `contents:body`, where body is all of the lines after the first
217
blank line. The optional GPG signature is `contents:signature`. The
218
first `N` lines of the message is obtained using `contents:lines=N`.
219
Additionally, the trailers as interpreted by linkgit:git-interpret-trailers[1]
220
-are obtained as 'trailers' (or by using the historical alias
221
-'contents:trailers').
220
+are obtained as `trailers` (or by using the historical alias
221
+`contents:trailers`).
222
223
For sorting purposes, fields with numeric values sort in numeric order
224
(`objectsize`, `authordate`, `committerdate`, `creatordate`, `taggerdate`).