Your message dated Wed, 04 Jun 2003 04:17:38 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#105285: fixed in gcc-3.3 1:3.3ds9-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sat, 17 May 2003 17:32:42 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#130415: fixed in gcc-3.3 1:3.3ds9-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sat, 17 May 2003 17:32:43 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#131454: fixed in gcc-3.3 1:3.3ds9-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sat, 17 May 2003 17:32:43 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#134558: fixed in gcc-3.3 1:3.3ds9-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sat, 17 May 2003 17:32:43 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#134558: fixed in gcc-3.3 1:3.3ds9-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sat, 17 May 2003 17:32:50 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#21255: fixed in gcc-3.3 1:3.3ds9-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sat, 17 May 2003 17:32:54 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#62309: fixed in gcc-3.3 1:3.3ds9-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sat, 17 May 2003 17:32:55 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#83221: fixed in gcc-3.3 1:3.3ds9-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sat, 17 May 2003 17:32:51 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#43001: fixed in gcc-3.3 1:3.3ds9-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sat, 17 May 2003 17:32:56 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#87540: fixed in gcc-3.3 1:3.3ds9-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Sat, 17 May 2003 17:32:57 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#94891: fixed in gcc-3.3 1:3.3ds9-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Processing commands for [EMAIL PROTECTED]:
> retitle 70743 [fixed in gcc-3.0 and gcc-3.1] [alpha] g++ -O2 optimization
> error
Bug#70743: [alpha] g++ -O2 optimization error
Changed Bug title.
> retitle 142844 [fixed in gcc-3.0 and gcc-3.1] [alpha] dead code removal in
> switch() broken
Bug#1428
Your message dated Mon, 04 Mar 2002 20:02:16 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#130394: fixed in gcc-2.95 2.95.4.ds9-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is
Processing commands for [EMAIL PROTECTED]:
> tags 128367 + fixed
Bug#128367: aspell: trigger internal compiler error on mipsel
Tags added: fixed
> retitle 128367 [fixed in g++-3.0] aspell: trigger internal compiler error on
> mipsel
Bug#128367: aspell: trigger internal compiler error on mipsel
C
tags 128367 + fixed
retitle 128367 [fixed in g++-3.0] aspell: trigger internal compiler error on
mipsel
thanks
Ryan Murray writes:
> I'm not sure whether we want to keep this open or not? I'm not sure what the
> change is, or how easy it might be to backport. Is there an easy way to
> find this
Processing commands for [EMAIL PROTECTED]:
> reassign 128367 g++-2.95
Bug#128367: aspell: trigger internal compiler error on mipsel
Bug reassigned from package `aspell' to `g++-2.95'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system adminis
reassign 128367 g++-2.95
thanks
This is c++/4234:
State-Changed-From-To: open->closed
State-Changed-By: lerdsuwa
State-Changed-When: Fri Nov 16 23:55:34 2001
Stat
17 matches
Mail list logo
