From: Nathan Sidwell <nathan@acm.org>
To: gcc@gcc.gnu.org
Subject: Re: [RFC] Update Stage 4 description
Date: Wed, 09 Jan 2019 15:14:00 -0000 [thread overview]
Message-ID: <9dce2bb5-6c92-848e-16d2-bbfaa6a579ef@acm.org> (raw)
In-Reply-To: <CAH6eHdQeM+G=ohOf4YKEzOeJyu_HWHW5htWMMDx6mJbGDgwFTg@mail.gmail.com>
On 1/9/19 4:02 AM, Jonathan Wakely wrote:
>> +extra care on not introducing new regressions - fixing bugs at all cost
>
> ISTM that this should be either "at any cost" or "at all costs". The
> current wording can't make up its mind if it's singular or plural.
Agreed, as a native english speaker, 'at any cost' would be my preferred
formulation.
> I also stumbled over "on not introducing" ... would that be better as
> "to not introduce"?
Either seems fine to me
nathan
--
Nathan Sidwell
next prev parent reply other threads:[~2019-01-09 15:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 8:41 Tom de Vries
2019-01-09 8:47 ` Richard Biener
2019-01-09 9:20 ` [wwwdocs, committed] " Tom de Vries
2019-01-09 9:02 ` [RFC] " Jonathan Wakely
2019-01-09 15:14 ` Nathan Sidwell [this message]
2019-01-09 14:16 ` Paul Koning
2019-01-09 14:31 ` Richard Biener
2019-01-09 16:33 ` Joseph Myers
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=9dce2bb5-6c92-848e-16d2-bbfaa6a579ef@acm.org \
--to=nathan@acm.org \
--cc=gcc@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).