ResourceManager: Do not double initalize the NepomukMainModel
Review Request #105281 - Created June 17, 2012 and submitted
ResourceManager: Do not double initalize the NepomukMainModel The NepomukMainModel is initalized once when it is created and then the second time in ResourceManager::init. This results in a second connection being made to nepomukstorage, and an extra thread being spawned over there. The old thread is eventually deleted, but the whole process is rather pointless.
Review request changed
Adding the 'release-team' to the groups as I missed the RC1 freeze. This change is very very trivial, but they sent an email saying they want to be informed.
To be honest i'd prefer you commit this to the KDE/4.9 branch after RC1 is released, as you say it's not critical (nothing breaks), so i don't really see the point on breaking the RC freeze.