Hi all,
Just my regular reminder regarding usage of QNetworkAccessManager in
your applications and libraries, especially when it comes to
interacting with kde.org infrastructure.
Unfortunately, from it's first iteration in Qt 4 QNetworkAccessManager
was shipped with a severe and fundamental defec
On Wednesday 13 July 2016 20:51:24 Christoph Feck wrote:
> On Wednesday 13 July 2016 20:12:46 Martin Koller wrote:
> > just wanted to let you know that I have now completed the
> > kolourpaint port to KF5 and this is now in its master branch. I
> > have also updated kde-build-metadata Hope I did al
On Wednesday 13 July 2016 20:24:42 Luigi Toscano wrote:
> Martin Koller ha scritto:
> > Hi all,
> >
> > just wanted to let you know that I have now completed the kolourpaint port
> > to KF5
> > and this is now in its master branch. I have also updated kde-build-metadata
> > Hope I did all correct
On Wednesday 13 July 2016 20:12:46 Martin Koller wrote:
> just wanted to let you know that I have now completed the
> kolourpaint port to KF5 and this is now in its master branch. I
> have also updated kde-build-metadata Hope I did all correct.
The about dialog says it is version 5.25.0 (=framewor
Martin Koller ha scritto:
> Hi all,
>
> just wanted to let you know that I have now completed the kolourpaint port to
> KF5
> and this is now in its master branch. I have also updated kde-build-metadata
> Hope I did all correct.
I'm going to update the i18n branches on repo-metadata (which gener
Hi all,
just wanted to let you know that I have now completed the kolourpaint port to
KF5
and this is now in its master branch. I have also updated kde-build-metadata
Hope I did all correct.
--
Best regards/Schöne Grüße
Martin
A: Because it breaks the logical sequence of discussion
Q: Why is t
