Processing commands for [email protected]:

> #
> # bts-link upstream status pull for source package webkit
> # 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 #594470 (http://bugs.debian.org/594470)
> #  * https://bugs.webkit.org/show_bug.cgi?id=44681
> #  * remote status changed: (?) -> NEW
> usertags 594470 + status-NEW
Bug#594470: libwebkit-1.0-2: CPU load goes to 100 % running JavaScript from 
http://tromey.com/Swirl/
There were no usertags set.
Usertags are now: status-NEW.
> # remote status report for #565992 (http://bugs.debian.org/565992)
> #  * https://bugs.webkit.org/show_bug.cgi?id=30508
> #  * remote status changed: UNCONFIRMED -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> forwarded 565992 https://bugs.webkit.org/show_bug.cgi?id=34063, 
> merged-upstream: https://bugs.webkit.org/show_bug.cgi?id=30508
Bug #565992 [libwebkit-1.0-2] libwebkit-1.0-2: invalid element name error for 
http XHTML pages declared as iso-8859-1
Changed Bug forwarded-to-address to 
'https://bugs.webkit.org/show_bug.cgi?id=34063, merged-upstream: 
https://bugs.webkit.org/show_bug.cgi?id=30508' from 
'https://bugs.webkit.org/show_bug.cgi?id=34063'
> usertags 565992 - status-UNCONFIRMED
Bug#565992: libwebkit-1.0-2: invalid element name error for http XHTML pages 
declared as iso-8859-1
Usertags were: status-UNCONFIRMED.
Usertags are now: .
> usertags 565992 + status-RESOLVED resolution-FIXED
Bug#565992: libwebkit-1.0-2: invalid element name error for http XHTML pages 
declared as iso-8859-1
There were no usertags set.
Usertags are now: status-RESOLVED resolution-FIXED.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
565992: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565992
Debian Bug Tracking System
Contact [email protected] with problems


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

Reply via email to