From: Derrick Stolee <stolee@gmail.com>
To: Junio C Hamano <gitster@pobox.com>,
Nils Leif Fischer via GitGitGadget <gitgitgadget@gmail.com>,
Derrick Stolee <dstolee@microsoft.com>
Cc: git@vger.kernel.org, Nils Leif Fischer <hello@nilsleiffischer.de>,
Nils Leif Fischer <nils.fischer@aei.mpg.de>
Subject: Re: [PATCH] Fix a typo in git-maintenance documentation
Date: Fri, 19 Mar 2021 14:37:38 -0400 [thread overview]
Message-ID: <8a73d5c2-831c-8e9e-5f21-2f8ef24dfa42@gmail.com> (raw)
In-Reply-To: <xmqqv99nm3jy.fsf@gitster.g>
On 3/19/2021 1:55 PM, Junio C Hamano wrote:
> "Nils Leif Fischer via GitGitGadget" <gitgitgadget@gmail.com>
>> gc::
>> Clean up unnecessary files and optimize the local repository. "GC"
>> - stands for "garbage collection," but this task performs many
>> + stands for "garbage collection", but this task performs many
>
> Isn't this merely an American style vs British style issue?
Yes, I believe so.
> https://www.grammarly.com/blog/quotation-marks
> https://www.thepunctuationguide.com/british-versus-american-style.html
> https://owl.purdue.edu/owl/general_writing/punctuation/quotation_marks/more_quotation_mark_rules.html
Specifically, this quote from your first link:
Commas and periods always go inside the quotation marks in
American English; dashes, colons, and semicolons almost always
go outside the quotation marks; question marks and exclamation
marks sometimes go inside, sometimes stay outside.
The only time I break this is when the exact string matters,
such as referencing an exact command with options. In those
cases, I try to restructure the sentence to avoid having a
comma or period outside of the quote.
Thanks,
-Stolee
next prev parent reply other threads:[~2021-03-19 18:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 10:17 [PATCH] Fix a typo in git-maintenance documentation Nils Leif Fischer via GitGitGadget
2021-03-19 17:55 ` Junio C Hamano
2021-03-19 18:37 ` Derrick Stolee [this message]
2021-03-19 20:19 ` Junio C Hamano
2021-03-20 1:55 ` Derrick Stolee
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8a73d5c2-831c-8e9e-5f21-2f8ef24dfa42@gmail.com \
--to=stolee@gmail.com \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=hello@nilsleiffischer.de \
--cc=nils.fischer@aei.mpg.de \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).