Thu, Jan 23
Wed, Jan 22
Tue, Jan 21
It's not a permission problem; it's "just" that the environment can't compile kdoctools anymore due to the requirements for a newer Qt, so all documentation which uses the newer entities fails.
Mon, Jan 20
Thanks! Do you think it would be possible to split the tox part (requirements, setup.py) from the partial porting (almost all changes under pology/) ?
Sun, Jan 19
Sat, Jan 18
Fri, Jan 17
Thu, Jan 16
Wed, Jan 15
if we copy applications.menu to plasma-workspace and patch it there, it will only be shipped with future plasma releases.
Then how about I copy this file applications.menu to plasma-workspace? After one or two years, we can delete this file from frameworks. But for compatibility, it will exist in both repositories for some time.
The question is the same. What happens with older Plasma with newer Frameworks?
It may be that nothing really breaks, of course.
Tue, Jan 14
Mon, Jan 13
Sun, Jan 12
Sat, Jan 11
Accepted if you amend the commit message; the full log from the build generation is probably overkill.
Fri, Jan 10
Thu, Jan 9
Wed, Jan 8
Mon, Jan 6
Sun, Jan 5
Fri, Jan 3
Thu, Jan 2
Wed, Jan 1
Tue, Dec 31
Landing it now - it's after christmas and I should have time in the next days/week to fix issues that we find.
As a reference for the future: this change broke the two weeks string freeze - which we haven't enforced so strongly in the past months, but please keep an eye on it. Expecially this time of the year with many countries on vacation.
Isn't it better to just use Qt::endl ?
I think it's much clearer to understand Qt::endl than QLatin1Char('\n')
But if we prefer to change to use \n it should be merged into the existing strings, doesn't make much sense to do
outStream << "</l:i18n>" << QLatin1Char('\n');
outStream << "</l:i18n>\n';
Mon, Dec 30
- when you commit something for another person, please use git commit --amend --author="John Doe <firstname.lastname@example.org>" and change the author. This is git and we can and must do it.
- we should not drop the 5 from the kcm and kio catalog names. It may be fine for Plasma stuff, as Plasma 5 and 6 may not be co-installable, but it is going to be a problem for KCM modules that can be co-installed. We discussed a similar problem in the past and the effort to fix this properly stalled. Please file a bug, raise the issue on the list (i18n-doc and plasma) but don't just silently remove the 5.