Anyway, back to GIMP hacking. And there comes the next oddity: I one again browsed all bugs and wasn't able to reproduce most of them. Either because they occur on some esoteric hardware or they simply don't occur on my hardware.
Well, this wouldn't be too bad if the bugs I can't reproduce didn't sound like stuff that prevent a fast realease (like SEGVs and FPEs in commonly used core functions).
Last but not least my reorganisation of the display shell re-broke "Shrink Wrap" and the shrink_wrap code looks like being designed around a dozend window manager bugs. needless to say that shrink_wrap works fine here, too.
Which leads me to the conclusion that it was a bad idea to configure my system to behave nicely. What I need is a broken X server, a broken window manager, a broken include and library structure and a non-broken hardware (since most people out there - including me - seem to hack on "broken" Intel machines).
But you didn't hear the worst thing yet: Today is a sunny day and I will not fix any bug but go out and enjoy the sun :-)
Have a nice sunday!
FOAF updates: Trust rankings are now exported, making the data available to other users and websites. An external FOAF URI has been added, allowing users to link to an additional FOAF file.
Keep up with the latest Advogato features by reading the Advogato status blog.
If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!