git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fabrizio Cucci <fabrizio.cucci@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: Back quote typo in error messages (?)
Date: Wed, 15 Feb 2017 21:51:30 +0000	[thread overview]
Message-ID: <CAOxYW4xqk4j6Uu86jq2Vi9Bpgihxfr2Tw-DQLc+7YTZiPmDtiA@mail.gmail.com> (raw)
In-Reply-To: <20170215212157.qgscyglgzrd5cplf@sigill.intra.peff.net>

On 15 February 2017 at 21:21, Jeff King <peff@peff.net> wrote:

> On Wed, Feb 15, 2017 at 09:06:46PM +0000, Fabrizio Cucci wrote:
>> Shouldn't the wrong flag be surrounded by two single quotes instead of
>> a back quote and a single quote?
>
> Some people use the matched backtick/single-quote to emulate the
> non-symmetric start/end quotes used in traditional typography (and in
> fact, ``foo'' in languages like asciidoc are typically rendered using
> smart-quotes).

I definitely didn't know about the use of them in traditional typography!
But I couldn't find any example of non-symmetric quotes in AsciiDoc...

> So I think what you are seeing is not wrong in the sense of being
> unintended by the author of the message.

I had the opposite impression from the quick search in the GitHub
repo, this is why I wrote here looking for some confirmation.

> I don't know how much we care about standardizing that punctuation.

I mentioned it was very minor but, still, in my opinion a project like
Git deserves consistent punctuation! :)

  parent reply	other threads:[~2017-02-15 21:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-15 21:06 Back quote typo in error messages (?) Fabrizio Cucci
2017-02-15 21:21 ` Jeff King
2017-02-15 21:31   ` Junio C Hamano
2017-02-15 21:51   ` Fabrizio Cucci [this message]
2017-02-15 21:56     ` Jeff King
2017-02-16 18:41       ` Fabrizio Cucci
2017-02-16 19:02         ` Jeff King
2017-02-16 20:58           ` Fabrizio Cucci

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAOxYW4xqk4j6Uu86jq2Vi9Bpgihxfr2Tw-DQLc+7YTZiPmDtiA@mail.gmail.com \
    --to=fabrizio.cucci@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).