From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
Cc: Bryan Evenson <bevenson@melinkcorp.com>,
Jon Mason <jdmason@kudzu.us>,
Yocto-mailing-list <yocto@lists.yoctoproject.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
OpenEmbedded Devel List
<openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] [OE-core] Inclusive Language Proposal for YP/OE
Date: Fri, 4 Feb 2022 20:12:23 +0100 [thread overview]
Message-ID: <CANNYZj86eHSn=5gcryZeVBS-qqqKKiafq5XyDO=nup-QdcF7iw@mail.gmail.com> (raw)
In-Reply-To: <lya6f6jx36.fsf@ensc-virt.intern.sigma-chemnitz.de>
[-- Attachment #1: Type: text/plain, Size: 629 bytes --]
On Fri, 4 Feb 2022 at 19:39, Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
wrote:
> > Would CANCEL be clearer to you than HALT?
>
> mmmh.... for me as a developer (and non-native english speaker), "cancel"
> means some ordered ending of an operation.
>
> But the condition above causes an emergency abort.
>
Cancel is the same as abort: a request to immediately stop the operation
(or not even start it) without reaching the originally requested outcome.
Halt implies the operation is not going to continue (Alan Turing was as
English as it gets, just to remind you).
I don't think any of this is remotely confusing.
Alex
[-- Attachment #2: Type: text/html, Size: 1077 bytes --]
next prev parent reply other threads:[~2022-02-04 19:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 16:17 Inclusive Language Proposal for YP/OE Jon Mason
2022-01-25 8:26 ` Paul Barker
2022-01-26 1:51 ` [yocto] " Paul Eggleton
2022-01-25 15:50 ` [OE-core] " Chuck Wolber
2022-01-25 16:00 ` [oe] " Ross Burton
2022-01-25 16:30 ` [oe] " Ross Burton
2022-01-26 8:37 ` Mikko.Rapeli
2022-01-25 23:07 ` [OE-core] " Randy MacLeod
2022-01-29 3:30 ` [oe] " Peter Kjellerstedt
2022-02-04 13:21 ` [OE-core] " Enrico Scholz
2022-02-04 13:58 ` [oe] " Alexander Kanavin
2022-02-04 14:16 ` Enrico Scholz
2022-02-04 15:01 ` Bryan Evenson
2022-02-04 18:38 ` Enrico Scholz
2022-02-04 19:12 ` Alexander Kanavin [this message]
2022-02-04 20:08 ` Enrico Scholz
2022-02-21 8:21 ` [oe] " Marta Rybczynska
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='CANNYZj86eHSn=5gcryZeVBS-qqqKKiafq5XyDO=nup-QdcF7iw@mail.gmail.com' \
--to=alex.kanavin@gmail.com \
--cc=bevenson@melinkcorp.com \
--cc=enrico.scholz@sigma-chemnitz.de \
--cc=jdmason@kudzu.us \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=yocto@lists.yoctoproject.org \
/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).