public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jason@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jason@gcc.gnu.org,
	martin@loewis.home.cs.tu-berlin.de, nobody@gcc.gnu.org,
	rankinc@zip.com.au
Subject: Re: c++/144: Exception handling bug (2): gcc-2.95.2 (unfixed from gcc-2.95.1)
Date: Tue, 19 Mar 2002 07:04:00 -0000	[thread overview]
Message-ID: <20020319150403.1642.qmail@sources.redhat.com> (raw)

Synopsis: Exception handling bug (2): gcc-2.95.2 (unfixed from gcc-2.95.1)

Responsible-Changed-From-To: unassigned->jason
Responsible-Changed-By: jason
Responsible-Changed-When: Tue Mar 19 07:04:01 2002
Responsible-Changed-Why:
    mine

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=144


             reply	other threads:[~2002-03-19 15:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-19  7:04 jason [this message]
2002-10-22 14:33 paolo
2002-10-22 14:36 Wolfgang Bangerth

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=20020319150403.1642.qmail@sources.redhat.com \
    --to=jason@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=martin@loewis.home.cs.tu-berlin.de \
    --cc=nobody@gcc.gnu.org \
    --cc=rankinc@zip.com.au \
    /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).