On Thursday, November 20, 2014 20:18:29 Burkhard Lück wrote:
> Am Donnerstag, 20. November 2014, 20:05:19 schrieb Sebastian Kügler:
> > On Thursday, November 20, 2014 19:57:54 Burkhard Lück wrote:
> > > > 2.2 is easier (if possible to change the code in 1 to do it) since it
> > > > does
> > > > not
On Tuesday, 2 December 2014 12:05:46 CEST, Jan Kundrát wrote:
[1] https://gerrit.vesnicky.cesnet.cz/r/167
Sorry for noise, that was a very bad example. A much better one is at
https://gerrit.vesnicky.cesnet.cz/r/164 .
Because that change has been merged now, the comments are shown collapsed.
Hi developers!
The KDE Gardening Team nominates one particular annoying bug as “The
Bug of the Month”, see https://community.kde.org/Gardening
This time, an annoying crash awaits investigation:
https://bugs.kde.org/show_bug.cgi?id=288410
Please help solving it, by adding ideas or patches to th
Howdy,
Today I was informed that Facebook has a tool similar in concept to Krazy,
called Flint [1]
You might want to read [1] and let me know if there are any checkers listed
there that
you'd like to see added to Krazy. Krazy already does many of the Flint checks,
but I'm interested in new ide
On Tuesday, 2 December 2014 19:46:18 CEST, Albert Astals Cid wrote:
Dependencies are the hard part. Any reason you didn't piggy-back on
build.kde.org for it?
That's right.
The reason for not using Jenkins was that the existing KDE's instance was
not up to that task without significant changes
El Dimarts, 2 de desembre de 2014, a les 12:05:46, Jan Kundrát va escriure:
> Hi,
> I managed to get a pre-merge continuous integration working with Gerrit.
> This means that whenever someone uploads/updates a change to Gerrit, it
> gets through a CI run and the result is reported back to Gerrit as
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/121213/
---
(Updated Dec. 2, 2014, 6:02 p.m.)
Review request for KDE Software on Mac
Hi,
I managed to get a pre-merge continuous integration working with Gerrit.
This means that whenever someone uploads/updates a change to Gerrit, it
gets through a CI run and the result is reported back to Gerrit as an
advice -- see e.g. [1] for an example. A KDE developer can still override
t
