public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: Jens.Maurer@gmx.net, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	mmitchel@gcc.gnu.org
Subject: Re: c++/1936: [2003-01-01] [New parser bug] pseudo-construction and >> operator
Date: Thu, 27 Mar 2003 15:46:00 -0000	[thread overview]
Message-ID: <20030327154015.768.qmail@sources.redhat.com> (raw)

Synopsis: [2003-01-01] [New parser bug] pseudo-construction and >> operator

State-Changed-From-To: analyzed->closed
State-Changed-By: bangerth
State-Changed-When: Thu Mar 27 15:40:15 2003
State-Changed-Why:
    Now fixed on mainline.

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


             reply	other threads:[~2003-03-27 15:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-27 15:46 bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-02 19:16 Mark Mitchell
2003-01-01 20:16 neil

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=20030327154015.768.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=Jens.Maurer@gmx.net \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=mmitchel@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).