From: Nathan Sidwell <nathan@codesourcery.com>
To: tbp <tbptbp@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: gcc/g++ 4.0.0, 20041205 snapshot, bug #18073 still present
Date: Tue, 07 Dec 2004 16:12:00 -0000 [thread overview]
Message-ID: <41B5D64E.7040201@codesourcery.com> (raw)
In-Reply-To: <4fc48eb104120706212dfbb1d6@mail.gmail.com>
tbp wrote:
> Hmm.
> I don't know what i'm supposed to do with a bug marked as resolved
> when it's not.
> I've added an entry http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18073
> some days ago, and got no sign of life.
> So i've reposted here, to no avail.
> Am i supposed to open a new bug in bugzilla?
I have reopened the bug. thanks for the report
nathan
--
Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery LLC
nathan@codesourcery.com :: http://www.planetfall.pwp.blueyonder.co.uk
prev parent reply other threads:[~2004-12-07 16:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 20:42 tbp
2004-12-07 14:21 ` tbp
2004-12-07 16:12 ` Nathan Sidwell [this message]
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=41B5D64E.7040201@codesourcery.com \
--to=nathan@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=tbptbp@gmail.com \
/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).