[13:31]  * MacSlow -> lunch
[15:39] <_ke> mat_t_, ping
[15:41] <mat_t_> _ke, hi
[15:41] <_ke> mat_t_, thanks for your hints: http://home.cs.tum.edu/~siegel/news/2009_07_28-bu-bu-bu-burst_mode
[15:42] <mat_t_> _ke, np, looks fantastic!
[15:43] <mat_t_> _ke: I like the icons, too
[15:43] <_ke> mat_t_, there is still some work left, but i like it too
[15:43] <mat_t_> _ke: good stuff
[15:44] <mat_t_> _ke: looking forward to testing that in Karmic
[15:44] <_ke> mat_t_, sure! would be great
[17:44] <djsiegel> mac_v: do you want to make sure round-5 paper cuts are forwarded upstream?
[17:45] <djsiegel> that would be really helpful, and would give you a break from the usual task of invalidating ppcs
[17:45] <mac_v> ???
[17:45] <mac_v> how?
[17:46] <djsiegel> perfect! a new think for you
[17:46] <djsiegel> new thing*
[17:47] <djsiegel> ok, basically, you find the corresponding bug in an upstream bug tracker
[17:47] <djsiegel> this is usually bugzilla.gnome.org
[17:47] <mac_v> i'm familiar with that ,... but bugzilla is a bigger mess...
[17:47] <djsiegel> if you find it, copy the URL, click "Affects project..." in launchpad, and it will let you paste the url in
[17:47] <djsiegel> yes I know
[17:47] <djsiegel> if you can't find the upstream bug, you file it
[17:47] <djsiegel> then make the link
[17:48] <djsiegel> once upstream knows about the bug, (1) they might work on it, and (2) people can find their way from the launchpad report to the upstream developers
[17:48] <mac_v> i'll try , for round 5 , i'll see what can be done
[17:48] <djsiegel> cool
[17:52] <kallepersson> Updated: http://files.getdropbox.com/u/107961/pdf-mod.png
[17:52] <kallepersson> Whoops, wrong channel.
[17:56]  * mac_v  feels , djsiegel needs to buy him a drink... since he's easing a lot of djsiegel's work ;p