public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/42966] add some indication that a warning has been converted to an error Date: Fri, 05 Feb 2010 01:20:00 -0000 [thread overview] Message-ID: <20100205012017.12176.qmail@sourceware.org> (raw) In-Reply-To: <bug-42966-13511@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from manu at gcc dot gnu dot org 2010-02-05 01:20 ------- @Simon, I think this solution would be accepted more readily by everybody, since anyway we already have the [-W*] markers for most warnings except default ones. What do you think? I specially like showing the flag for disabling but that would be perhaps more transgressive. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42966
next prev parent reply other threads:[~2010-02-05 1:20 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-02-05 1:16 [Bug other/42966] New: " manu at gcc dot gnu dot org 2010-02-05 1:20 ` manu at gcc dot gnu dot org [this message] 2010-02-07 20:58 ` [Bug other/42966] " pinskia at gcc dot gnu dot org 2010-02-27 18:49 ` manu at gcc dot gnu dot org 2010-04-14 16:08 ` manu at gcc dot gnu dot org 2010-04-14 16:10 ` manu at gcc dot gnu dot org
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=20100205012017.12176.qmail@sourceware.org \ --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: linkBe 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).