Re: [Development] ABICC results for 5.3.0 alpha (qtbase)

2014-03-06 Thread Giuseppe D'Angelo
Hi Andrey, Il 06/03/2014 18:00, Andrey Ponomarenko ha scritto: I think, it's better to create a single report in order to avoid duplicated data in your reports. For example, the QtConcurrent and QtCore header files recursively include intersected sets of symbols and therefore corresponding repor

Re: [Development] ABICC results for 5.3.0 alpha (qtbase)

2014-03-06 Thread Andrey Ponomarenko
Hi Giuseppe, I think, it's better to create a single report in order to avoid duplicated data in your reports. For example, the QtConcurrent and QtCore header files recursively include intersected sets of symbols and therefore corresponding reports show the same changes. Example of alternative

Re: [Development] Nominating Ulf Hermann as approver

2014-03-06 Thread Mohamed Fawzi
+1 On 4 Mar 2014, at 13:51, Simon Hausmann wrote: > Hi, > > I'd like to nominate Ulf for approvership. He's been hacking on various bits > and pieces in the profiler support in Qml and he also implemented a brand new > profiler for the JavaScript engine. > > I'm convinced that he would make a

Re: [Development] Missing documentation

2014-03-06 Thread Marc Mutz
On Tuesday 04 March 2014 12:38:29 Samuel Gaist wrote: > Hi, > > On 4 mars 2014, at 10:16, Marc Mutz wrote: > >>QWidget::macCGHandle() > > Currently not implemented, used to return the Core Graphics Handle for the > widget > > >>QWidget::macQDHandle() > > Also not implemented, used to r

Re: [Development] CI Broken for 4.8

2014-03-06 Thread Shaw Andy
I was informed earlier in the week that it was known and being investigated, there was a problem with the Mac OS X 10.6 machine but I was also under the impression that it would be fixed already by now so I don't know what is happening with it at the moment. Andy From: development-bounces+andy

[Development] CI Broken for 4.8

2014-03-06 Thread Richard Moore
Hi, CI appears to be broken for 4.8, for example the following changes (separate CI runs) have failed on the same tests even though one is just a doc fix: https://codereview.qt-project.org/#change,79247 https://codereview.qt-project.org/#change,78289 It appears to the macos node that is stuck. L