Processed: gcc: submitted Debian report #203351 to gcc-gnats as PR 11713

To: doko@debian.org
Cc: debian-bugs-forwarded@lists.debian.org (#203351), Debian GCC maintainers <debian-gcc@lists.debian.org>(g++-3.3 #203351)
Subject: Processed: gcc: submitted Debian report #203351 to gcc-gnats as PR 11713
From: owner@bugs.debian.org (Debian Bug Tracking System)
Date: Tue, 29 Jul 2003 14:48:08 -0500
Message-id: <[🔎] handler.s.C.10595080495980.transcript@bugs.debian.org>
In-reply-to: <E19haRO-0003Hc-33@tango.net.local>
References: <E19haRO-0003Hc-33@tango.net.local>

Processing commands for control@bugs.debian.org:

> # submitted Debian report #203351 to gcc-gnats as PR 11713
> # http://gcc.gnu.org/PR11713
> forwarded 203351 http://gcc.gnu.org/PR11713
Bug#203351: g++-3.3: Broken parser
Noted your statement that Bug has been forwarded to http://gcc.gnu.org/PR11713.

> retitle 203351 [PR 11713] [3.3/3.4 regression] c++ parser error
Bug#203351: g++-3.3: Broken parser
Changed Bug title.

> tags 203351 + upstream
Bug#203351: [PR 11713] [3.3/3.4 regression] c++ parser error
There were no tags set.
Tags added: upstream

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Reply to:

Prev by Date: Re: should bugs really be closed?
Next by Date: [Bug c++/11713] [3.3/3.4 regression] c++ parser error
Previous by thread: [Bug optimization/11634] [3.3/3.4 regression] [hppa] ICE in verify_local_live_at_start, at flow.c:555
Next by thread: [Bug c++/11713] [3.3/3.4 regression] c++ parser error
Index(es):
- Date
- Thread