From: Joseph Myers <joseph@codesourcery.com>
To: Jeff Law <law@redhat.com>
Cc: Prathamesh Kulkarni <prathamesh.kulkarni@linaro.org>,
gcc Patches <gcc-patches@gcc.gnu.org>,
Marek Polacek <polacek@redhat.com>
Subject: Re: [ping * 2] PR78736: New C warning -Wenum-conversion
Date: Thu, 29 Jun 2017 23:01:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1706292300530.22519@digraph.polyomino.org.uk> (raw)
In-Reply-To: <f5e584df-c01d-9718-a1d9-713cbc914dec@redhat.com>
On Thu, 29 Jun 2017, Jeff Law wrote:
> On 05/23/2017 07:54 AM, Prathamesh Kulkarni wrote:
> > Hi,
> > I would like to ping this patch for review:
> > https://gcc.gnu.org/ml/gcc-patches/2017-05/msg00775.html
> So was there any kind of resolution on the case in libcomp where we had
> an assignment between two essentially equivalent, but distinct enums?
I don't know. I approved this patch on the 12th subject to one
correction, but see it hasn't yet been committed.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2017-06-29 23:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 14:13 Prathamesh Kulkarni
2017-06-29 22:04 ` Jeff Law
2017-06-29 23:01 ` Joseph Myers [this message]
2017-06-30 15:21 ` Jeff Law
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=alpine.DEB.2.20.1706292300530.22519@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=polacek@redhat.com \
--cc=prathamesh.kulkarni@linaro.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).