public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: paolo@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, j.vanbemmel@home.nl, neil@daikokuya.co.uk, nobody@gcc.gnu.org, pfeifer@dbai.tuwien.ac.at Subject: Re: optimization/9086: Missing attachment for #9085 Date: Sat, 28 Dec 2002 14:12:00 -0000 [thread overview] Message-ID: <20021228221229.19384.qmail@sources.redhat.com> (raw) Synopsis: Missing attachment for #9085 State-Changed-From-To: open->closed State-Changed-By: paolo State-Changed-When: Sat Dec 28 14:12:29 2002 State-Changed-Why: Ok, having completed optimization/9085, I'm closing this one, but please make notice of Neil's remark. Paolo. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9086
next reply other threads:[~2002-12-28 22:12 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-28 14:12 paolo [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-12-28 13:56 j.vanbemmel
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=20021228221229.19384.qmail@sources.redhat.com \ --to=paolo@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=j.vanbemmel@home.nl \ --cc=neil@daikokuya.co.uk \ --cc=nobody@gcc.gnu.org \ --cc=pfeifer@dbai.tuwien.ac.at \ /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).