public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sebpop at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/39262] [miro] - Revision 144368 - Werror in ../miro/gcc/genconstants.c Date: Sun, 22 Feb 2009 14:55:00 -0000 [thread overview] Message-ID: <20090222145504.14112.qmail@sourceware.org> (raw) In-Reply-To: <bug-39262-13830@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from sebpop at gmail dot com 2009-02-22 14:55 ------- Subject: Re: [miro] - Revision 144368 - Werror in ../miro/gcc/genconstants.c I will fix this with the attached patch when approved. ------- Comment #6 from sebpop at gmail dot com 2009-02-22 14:55 ------- Created an attachment (id=17342) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17342&action=view) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39262
next prev parent reply other threads:[~2009-02-22 14:55 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-02-22 3:03 [Bug bootstrap/39262] New: " rob1weld at aol dot com 2009-02-22 7:40 ` [Bug bootstrap/39262] " ubizjak at gmail dot com 2009-02-22 12:25 ` pinskia at gcc dot gnu dot org 2009-02-22 12:51 ` rob1weld at aol dot com 2009-02-22 12:56 ` steven at gcc dot gnu dot org 2009-02-22 14:55 ` sebpop at gmail dot com [this message] 2009-02-22 20:39 ` rob1weld at aol dot com
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=20090222145504.14112.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).