public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: mmitchel@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/1936: [2003-01-01] [New parser bug] pseudo-construction and >> operator
Date: Thu, 02 Jan 2003 19:16:00 -0000	[thread overview]
Message-ID: <20030102191601.23133.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/1936; it has been noted by GNATS.

From: Mark Mitchell <mark@codesourcery.com>
To: "neil@gcc.gnu.org" <neil@gcc.gnu.org>,
   "Jens.Maurer@gmx.net" <Jens.Maurer@gmx.net>,
   "gcc-bugs@gcc.gnu.org" <gcc-bugs@gcc.gnu.org>,
   "gcc-prs@gcc.gnu.org" <gcc-prs@gcc.gnu.org>,
   "mmitchel@gcc.gnu.org" <mmitchel@gcc.gnu.org>,
   "nobody@gcc.gnu.org" <nobody@gcc.gnu.org>,
   "gcc-gnats@gcc.gnu.org" <gcc-gnats@gcc.gnu.org>
Cc:  
Subject: Re: c++/1936: [2003-01-01] [New parser bug] pseudo-construction and
 >> operator
Date: Thu, 02 Jan 2003 11:11:11 -0800

 --On Wednesday, January 01, 2003 08:16:07 PM +0000 "neil@gcc.gnu.org" 
 <neil@gcc.gnu.org> wrote:
 
 > Synopsis: [2003-01-01] [New parser bug] pseudo-construction and >>
 > operator
 >
 > Responsible-Changed-From-To: unassigned->mmitchel
 > Responsible-Changed-By: neil
 > Responsible-Changed-When: Wed Jan  1 12:16:06 2003
 > Responsible-Changed-Why:
 >     Mark, can I give you this?
 
 Yes, but since it's not a regression I'm not going to worry about it
 any time soon.
 
 Thanks,
 
 -- 
 Mark Mitchell                mark@codesourcery.com
 CodeSourcery, LLC            http://www.codesourcery.com


             reply	other threads:[~2003-01-02 19:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-02 19:16 Mark Mitchell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-27 15:46 bangerth
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=20030102191601.23133.qmail@sources.redhat.com \
    --to=mark@codesourcery.com \
    --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).