public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/48956] -Wconversion should warn when a complex value is assigned to a real result
Date: Thu, 12 May 2011 23:18:00 -0000	[thread overview]
Message-ID: <bug-48956-4-f5oAg386zB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48956-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48956

--- Comment #7 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2011-05-12 23:06:14 UTC ---
(In reply to comment #6)
> Thanks, I was somewhat aware of the additional requirements for applying
> patches to the official tree (probably I should also file a copyright
> assignment), but I wanted to check with you that I was on the right track
> first.   I'm a bit swamped this week, but should be able to do all this next
> week.

You should definitely get the copyright assignment, but you do not need to wait
for it to submit the patch properly and get more feedback and approval.


  parent reply	other threads:[~2011-05-12 23:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-11  3:26 [Bug c/48956] New: " stevenj at alum dot mit.edu
2011-05-11  0:11 ` [Bug c/48956] " stevenj at alum dot mit.edu
2011-05-11  8:27 ` manu at gcc dot gnu.org
2011-05-11  8:50 ` manu at gcc dot gnu.org
2011-05-11 20:34 ` stevenj at alum dot mit.edu
2011-05-11 22:08 ` manu at gcc dot gnu.org
2011-05-11 22:39 ` manu at gcc dot gnu.org
2011-05-12 23:11 ` stevenj at alum dot mit.edu
2011-05-12 23:18 ` manu at gcc dot gnu.org [this message]
2012-03-24 19:15 ` manu at gcc dot gnu.org
2014-11-07 10:14 ` paolo.carlini at oracle dot com
2015-01-01 18:15 ` maltsevm at gmail dot com
2015-05-15 18:03 ` miyuki at gcc dot gnu.org
2015-05-15 18:47 ` manu at gcc dot gnu.org
2015-06-24 21:53 ` matt at bitbashing dot io
2015-06-24 22:08 ` manu at gcc dot gnu.org
2015-06-24 22:13 ` matt at bitbashing dot io

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=bug-48956-4-f5oAg386zB@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).