Re: [PATCH 3/6] git-check-ref-format.txt: avoid single quote

From: Felipe Contreras <felipe.contreras@gmail.com>
Date: May 14, 2021, 12:30 UTC
Message-ID: <609e6d4d67f90_4312720862@natae.notmuch>
In-Reply-To: <CAN0heSqsrUU=GYsckhZT7Dvx=Rh3aWMMTMBLBfy2XuDWYpQPFg@mail.gmail.com>

Martin Ågren wrote:

> On Fri, 14 May 2021 at 00:00, Junio C Hamano <gitster@pobox.com> wrote:

Show 12 quoted lines

> > The proposed log message did not explain why you wanted to avoid
> > double-quote pair on the "cat-file" line.  Is this meant as a
> > workaround for the "single quotes are shown around git cat-file"
> > issue?
> 
> Hmm, I've somehow tended to think that it's 'git foo' the tool and `git
> foo --bar baz` the actual invocation. SQs for the former, backticks for
> the latter. Like, `git cat-file` is not a correct invocation of 'git
> cat-file'. But I think I'm starting to see the error in my ways --
> CodingGuidelines says to use backticks around command names, so it
> really should be `git cat-file`. And changing that might just happen to
> avoid the issue that triggered this patch.

Hmmm. `git status`, `git branch`, `git diff`, `git log`.

All these are both "tools" **and** invocations. In fact, you an pretty much "invoke" any thing: `git checkout` might not do anything... But it runs.

-- 
Felipe Contreras