Taylor Blau <me@xxxxxxxxxxxx> writes: > "'"- (single-quote) styled code fencing is no longer considered modern > within the "Documentation/" subtree. > > In preparation for adding additional information to this section of > git-for-each-ref(1)'s documentation, update old-style code fencing to > use "`"-style fencing instead. Is this just me who wants to do s/fenc/quot/g? Unless somebody objects, I'd do so while queuing. Thanks. > > Signed-off-by: Taylor Blau <me@xxxxxxxxxxxx> > --- > Documentation/git-for-each-ref.txt | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git a/Documentation/git-for-each-ref.txt b/Documentation/git-for-each-ref.txt > index 323ce07de..1279b9733 100644 > --- a/Documentation/git-for-each-ref.txt > +++ b/Documentation/git-for-each-ref.txt > @@ -213,12 +213,12 @@ and `date` to extract the named component. > The complete message in a commit and tag object is `contents`. > 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 > -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 > first `N` lines of the message is obtained using `contents:lines=N`. > Additionally, the trailers as interpreted by linkgit:git-interpret-trailers[1] > -are obtained as 'trailers' (or by using the historical alias > -'contents:trailers'). > +are obtained as `trailers` (or by using the historical alias > +`contents:trailers`). > > For sorting purposes, fields with numeric values sort in numeric order > (`objectsize`, `authordate`, `committerdate`, `creatordate`, `taggerdate`).
