public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/38182] stddef.h assumes machinee/ansi.h defines _ANSI_H_
Date: Tue, 24 Mar 2009 16:04:00 -0000 [thread overview]
Message-ID: <20090324160438.13248.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38182-15541@http.gcc.gnu.org/bugzilla/>
------- Comment #13 from joseph at codesourcery dot com 2009-03-24 16:04 -------
Subject: Re: stddef.h assumes machinee/ansi.h defines
_ANSI_H_
On Tue, 24 Mar 2009, aran at 100acres dot us wrote:
> Joseph,
> The fixincludes changes fix another issue. Should I create
> a new bug and reference that bug in the e-mail or just
> describe the problem in the e-mail?
Describing the problem in the email is sufficient. If the patch isn't
reviewed within a week or so then ping it (as many times as needed). If
the patch is approved but not committed, make clear that you need someone
with write access to commit it for you.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38182
next prev parent reply other threads:[~2009-03-24 16:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 20:31 [Bug c/38182] New: " aran at 100acres dot us
2008-11-19 20:34 ` [Bug c/38182] " aran at 100acres dot us
2009-02-11 4:32 ` [Bug target/38182] " hbent at cs dot oberlin dot edu
2009-02-19 21:46 ` aran at 100acres dot us
2009-03-23 19:31 ` prlw1 at cam dot ac dot uk
2009-03-23 20:35 ` joseph at codesourcery dot com
2009-03-23 20:45 ` prlw1 at cam dot ac dot uk
2009-03-23 20:54 ` joseph at codesourcery dot com
2009-03-23 21:07 ` prlw1 at cam dot ac dot uk
2009-03-24 6:16 ` aran at 100acres dot us
2009-03-24 13:22 ` joseph at codesourcery dot com
2009-03-24 13:32 ` joseph at codesourcery dot com
2009-03-24 15:49 ` aran at 100acres dot us
2009-03-24 16:04 ` joseph at codesourcery dot com [this message]
2009-03-25 18:57 ` prlw1 at cam dot ac dot uk
2009-09-07 16:47 ` prlw1 at cam dot ac dot uk
2009-09-07 17:25 ` joseph at codesourcery 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=20090324160438.13248.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: 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).