From: Mark Eggleston <mark.eggleston@codethink.co.uk>
To: sgk@troutmask.apl.washington.edu
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, fortran <fortran@gcc.gnu.org>
Subject: Re: [PATCH, Fortran] Optionally suppress no-automatic overwrites recursive warning - for approval
Date: Mon, 21 Oct 2019 13:39:00 -0000 [thread overview]
Message-ID: <8314be8a-dbad-d693-7675-4da75c43886a@codethink.co.uk> (raw)
In-Reply-To: <f84fe6e2-2fa1-1a42-a569-78981a290673@codethink.co.uk>
PING - OK to commit?
On 02/10/2019 09:00, Mark Eggleston wrote:
>
> On 28/09/2019 17:50, Steve Kargl wrote:
>> On Thu, Sep 26, 2019 at 09:45:28AM +0100, Mark Eggleston wrote:
>>> Original thread starts here
>>> https://gcc.gnu.org/ml/gcc-patches/2019-09/msg01185.html
>>>
>>> OK to commit?
>>>
>> I'm not a big fan of option proliferation. If you don't
>> want to see warns just use -w. Of course, this is just
>> MHO.
> Unfortunately -w switches off ALL warnings.
>
--
https://www.codethink.co.uk/privacy.html
next prev parent reply other threads:[~2019-10-21 13:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 8:45 Mark Eggleston
2019-09-28 16:50 ` Steve Kargl
2019-10-02 8:00 ` Mark Eggleston
2019-10-21 13:39 ` Mark Eggleston [this message]
2019-10-25 8:44 ` Tobias Burnus
2019-10-25 13:34 ` Jeff Law
2019-10-25 14:17 ` Tobias Burnus
2019-10-25 14:53 ` Jeff Law
2019-10-25 18:38 ` Argument-mismatch fallout (was: Re: [PATCH, Fortran] Optionally suppress no-automatic overwrites recursive warning - for approval) Tobias Burnus
2019-10-25 19:07 ` Argument-mismatch fallout Thomas Koenig
2019-10-25 14:36 ` [PATCH, Fortran] Optionally suppress no-automatic overwrites recursive warning - for approval Steve Kargl
2019-10-25 15:47 ` Tobias Burnus
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=8314be8a-dbad-d693-7675-4da75c43886a@codethink.co.uk \
--to=mark.eggleston@codethink.co.uk \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=sgk@troutmask.apl.washington.edu \
/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).