From: Samuel Wales <samologist@gmail.com>
To: Adam Porter <adam@alphapapa.net>
Cc: Ihor Radchenko <yantar92@posteo.net>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
Bastien <bzg@gnu.org>
Subject: Re: [WORG] 2680e65 * org-maintenance.org (Copyright assignments): Minor improvements
Date: Tue, 2 Apr 2024 17:39:54 -0700 [thread overview]
Message-ID: <CAJcAo8s2krK=_Gz7NyESPEkOjZv=+nTt0cbg_eF=SKSHBjmfog@mail.gmail.com> (raw)
In-Reply-To: <0f35e14b-1961-4e62-b9ba-b1161e67afad@alphapapa.net>
[-- Attachment #1: Type: text/plain, Size: 965 bytes --]
not following this.
but it amused me:
>> In rare cases, an inquiry from an
>> +Org maintainer gets the process moving again.
>
> may be missing something, but the last sentence now reads like our
>(Org maintainer's) inquiry rarely works.
while it can definitely read that way, to me as a native speaker at least,
it is reasonably ok, although ambiguous. it is saying, somewhat casually,
that in rare cases it is /needed/ for the org maintainer to intervene and
he or she does so successfully or so. removing ambiguity would help, but
nto a huge deal.
apropos of nothing, ambiguity should be eliminated from medical textbooks
and papers. "rarely, ...." can be interpreted like, it's rare so look for
horses not zebras [neglecting that zebras exist], or it's rare but consider
it and find out more about it, or various other things.
--
The Kafka Pandemic
A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com
[-- Attachment #2: Type: text/html, Size: 1238 bytes --]
next prev parent reply other threads:[~2024-04-03 0:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-24 12:35 [WORG] 2680e65 * org-maintenance.org (Copyright assignments): Minor improvements Ihor Radchenko
2024-03-24 17:55 ` Bastien Guerry
2024-03-24 18:26 ` Ihor Radchenko
2024-03-25 8:17 ` Bastien Guerry
2024-03-25 14:17 ` Adam Porter
2024-03-26 14:59 ` Ihor Radchenko
2024-03-27 3:23 ` Adam Porter
2024-03-28 12:01 ` Ihor Radchenko
2024-03-28 12:49 ` Adam Porter
2024-03-28 13:11 ` Ihor Radchenko
2024-03-29 18:17 ` Bastien Guerry
2024-03-30 11:08 ` Ihor Radchenko
2024-03-31 15:46 ` Adam Porter
2024-04-02 11:20 ` Ihor Radchenko
2024-04-02 23:01 ` Adam Porter
2024-04-03 0:39 ` Samuel Wales [this message]
2024-04-03 12:20 ` Ihor Radchenko
2024-04-03 12:18 ` Ihor Radchenko
2024-05-08 12:12 ` Ihor Radchenko
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: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJcAo8s2krK=_Gz7NyESPEkOjZv=+nTt0cbg_eF=SKSHBjmfog@mail.gmail.com' \
--to=samologist@gmail.com \
--cc=adam@alphapapa.net \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).