2013/8/14 Darrell Anderson <darrella@hushmail.com>
Creating patches went surprisingly smooth. The final list is short:

tdelibs
tdebase
tdeartwork
tdesdk
tde-style-lipstik
tde-style-qtcurve
koffice
tde-i18n

I had no build errors. A superficial test of selecting the styles
in kcontrol resulted in no errors or problems.

Caveat: The tde-i18n patch is huge. So huge that I will not even
try to post the patch or try to push to git until I reduce to
smaller patches and push piece-meal one at a time.

That said, how do we want to proceed next? I can post the patches
online and somebody else could test. Or I could just push to git
and listen for screams of pain and anguish. No problems noticed
here, but I'm only one person with my own perspective.
I don't feel that I'm one of core testers, but why not to push them into their own branch and let somebody test it? 
IMO It's easier than mess with patch-sets and no mob of angry developers or testers will not want to broke your legs ;)

btw: haven't forgot to rename cmake variables? e.g. in tdeartwork...