mirrors/git
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc: use "<literal>"-style quoting for literal strings

Browse Source 
"'<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>
This commit is contained in:
Taylor Blau
2017-10-01 09:18:50 -07:00
committed by Junio C Hamano
parent 85cd4bb319
commit ced1f08b7b
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
Documentation/git-for-each-ref.txt
View File

@ -213,12 +213,12 @@ and `date` to extract the named component.
The complete message in a commit and tag object is `contents`. The complete message in a commit and tag object is `contents`.
Its first line is `contents:subject`, where subject is the concatenation Its first line is `contents:subject`, where subject is the concatenation
of all lines of the commit message up to the first blank line. The next of all lines of the commit message up to the first blank line. The next
line is 'contents:body', where body is all of the lines after the first line is `contents:body`, where body is all of the lines after the first
blank line. The optional GPG signature is `contents:signature`. The blank line. The optional GPG signature is `contents:signature`. The
first `N` lines of the message is obtained using `contents:lines=N`. first `N` lines of the message is obtained using `contents:lines=N`.
Additionally, the trailers as interpreted by linkgit:git-interpret-trailers[1] Additionally, the trailers as interpreted by linkgit:git-interpret-trailers[1]
are obtained as 'trailers' (or by using the historical alias are obtained as `trailers` (or by using the historical alias
'contents:trailers'). `contents:trailers`).
For sorting purposes, fields with numeric values sort in numeric order For sorting purposes, fields with numeric values sort in numeric order
(`objectsize`, `authordate`, `committerdate`, `creatordate`, `taggerdate`). (`objectsize`, `authordate`, `committerdate`, `creatordate`, `taggerdate`).