Processing commands for [email protected]:

> #
> # bts-link upstream status pull for source package gcc-4.3
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg00001.html
> #
> user [email protected]
Setting user to [email protected] (was 
[email protected]).
> # remote status report for #518751
> #  * http://gcc.gnu.org/PR37436
> #  * remote status changed: NEW -> REOPENED
> forwarded 518751 http://gcc.gnu.org/PR36415, merged-upstream: 
> http://gcc.gnu.org/PR37436
Bug#518751: g++-4.3 ICE on armel
Bug#484053: [PR target/36415] g++-4.3: [4.1/4.2 regression, armel] ICE in 
extract_insn, at recog.c:1990
Forwarded-to-address changed from http://gcc.gnu.org/PR36415 to 
http://gcc.gnu.org/PR36415, merged-upstream: http://gcc.gnu.org/PR37436.

> usertags 518751 - status-NEW
Bug#518751: g++-4.3 ICE on armel
Usertags were: status-NEW.
Usertags are now: .
> usertags 518751 + status-REOPENED
Bug#518751: g++-4.3 ICE on armel
There were no usertags set.
Usertags are now: status-REOPENED.
> # remote status report for #518751
> #  * http://gcc.gnu.org/PR37436
> #  * remote status changed: NEW -> REOPENED
> forwarded 518751 http://gcc.gnu.org/PR36415, merged-upstream: 
> http://gcc.gnu.org/PR37436
Bug#518751: g++-4.3 ICE on armel
Bug#484053: [PR target/36415] g++-4.3: [4.1/4.2 regression, armel] ICE in 
extract_insn, at recog.c:1990
Forwarded-to-address changed from http://gcc.gnu.org/PR36415, merged-upstream: 
http://gcc.gnu.org/PR37436 to http://gcc.gnu.org/PR36415, merged-upstream: 
http://gcc.gnu.org/PR37436.

> usertags 518751 - status-NEW
Bug#518751: g++-4.3 ICE on armel
Usertags were: status-REOPENED.
Usertags are now: status-REOPENED.
> usertags 518751 + status-REOPENED
Bug#518751: g++-4.3 ICE on armel
Usertags were: status-REOPENED.
Usertags are now: status-REOPENED.
> thanks
Stopping processing here.

Please contact me if you need assistance.

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


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to