[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Processed: [bts-link] source package gcc-6



Processing commands for control@bugs.debian.org:

> #
> # bts-link upstream status pull for source package gcc-6
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg00001.html
> #
> user bts-link-upstream@lists.alioth.debian.org
Setting user to bts-link-upstream@lists.alioth.debian.org (was bts-link-devel@lists.alioth.debian.org).
> # remote status report for #823938 (http://bugs.debian.org/823938)
> # Bug title: gcc -E has __DATE__/__TIME__ as Jan 1 1970 00:00:00
> #  * http://gcc.gnu.org/PR71183
> #  * remote status changed: NEW -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 823938 + fixed-upstream
Bug #823938 [gcc-6] gcc -E has __DATE__/__TIME__ as Jan 1 1970 00:00:00
Added tag(s) fixed-upstream.
> usertags 823938 - status-NEW
Usertags were: status-NEW.
Usertags are now: .
> usertags 823938 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: resolution-FIXED status-RESOLVED.
> # remote status report for #823938 (http://bugs.debian.org/823938)
> # Bug title: gcc -E has __DATE__/__TIME__ as Jan 1 1970 00:00:00
> #  * http://gcc.gnu.org/PR71183
> #  * remote status changed: NEW -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 823938 + fixed-upstream
Bug #823938 [gcc-6] gcc -E has __DATE__/__TIME__ as Jan 1 1970 00:00:00
Ignoring request to alter tags of bug #823938 to the same tags previously set
> usertags 823938 - status-NEW
Usertags were: status-RESOLVED resolution-FIXED.
Usertags are now: status-RESOLVED resolution-FIXED.
> usertags 823938 + status-RESOLVED resolution-FIXED
Usertags were: resolution-FIXED status-RESOLVED.
Usertags are now: resolution-FIXED status-RESOLVED.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
823938: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823938
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems


Reply to: