Re: [PATCH v4 4/6] doc: use modern "`"-style code fencing

From: Junio C Hamano <gitster@pobox.com>
Date: Oct 2, 2017, 01:35 UTC
Message-ID: <xmqqtvziqqku.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <20171002000630.GA63556@D-10-157-251-166.dhcp4.washington.edu>

Taylor Blau <me@ttaylorr.com> writes:

Show 9 quoted lines

>> Is this just me who wants to do s/fenc/quot/g?  Unless somebody
>> objects, I'd do so while queuing.
>
> I don't object, I think that fencing is less appropriate than quoting.
> I couldn't find the term myself when writing this commit :-).
>
> I am happy to send out v5 of this patch series with this commit
> re-written, or you can change it while queuing. Whichever is easier for
> you.

Just FYI, here is what I ended up with. I do not think this is about "modern" vs "old style"; it is more about using the more appropriate mark-up and our desire has always been to use `literal` for things that users need to type literally.

I notice that I didn't remove 'modern' from the title in the versoin below, though.

Thanks.

commit a184d836bcf1a557520095a90b22edf659ee88f2
Author: Taylor Blau <me@ttaylorr.com>
Date:   Sun Oct 1 09:18:50 2017 -0700

    doc: use modern "`<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>