From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] docs: use "currently" for the present time
Date: Mon, 20 Jan 2020 21:53:26 +0000 [thread overview]
Message-ID: <20200120215326.GE6570@camp.crustytoothpaste.net> (raw)
In-Reply-To: <alpine.LFD.2.21.2001201633240.8488@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]
On 2020-01-20 at 21:33:58, Robert P. J. Day wrote:
> On Mon, 20 Jan 2020, brian m. carlson wrote:
>
> > In many languages, the adverb with the root "actual" means "at the
> > present time." However, this usage is considered dated or even archaic
> > in English, and for referring to events occurring at the present time,
> > we usually prefer "currently" or "presently". "Actually" is commonly
> > used in modern English only for the meaning of "in fact" or to express a
> > contrast with what is expected.
>
> ... snip ...
>
> as someone who is constantly being sheldon cooper-level pedantic, i
> totally agree with this sentiment.
As I mentioned, this is very minor and I can't imagine a native English
speaker being confused by it, nor can I imagine a speaker of most
European languages finding it confusing. It just stood out to me since
I know Spanish and French and I thought, "Oh, someone was thinking in
another language here."
I've actually been sitting on this patch for a while because I thought
it might be too minor to send, but I finally decided to do it as I was
sending some other doc patches.
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 868 bytes --]
next prev parent reply other threads:[~2020-01-20 21:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 21:21 [PATCH] docs: use "currently" for the present time brian m. carlson
2020-01-20 21:33 ` Robert P. J. Day
2020-01-20 21:53 ` brian m. carlson [this message]
2020-01-21 18:42 ` Junio C Hamano
2020-01-21 19:10 ` Philip Oakley
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=20200120215326.GE6570@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/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).