On 19 March 2017 at 20:01, Thiago Macieira
mailto:thiago.macie...@intel.com>> wrote:
>> The rules are that only Qt Company people can import 3rdparty code, so I know
>> I am not responsible.
>>
>> Who do I assign the bug to?
>> https://bugreports.qt.io/browse/QTBUG-59586
QUIP 4 (see below) should
On 19 March 2017 at 20:01, Thiago Macieira
wrote:
> The rules are that only Qt Company people can import 3rdparty code, so I
> know
> I am not responsible.
>
> Who do I assign the bug to?
> https://bugreports.qt.io/browse/QTBUG-59586
For QTBUG-59586, I have https://codereview.qt-project.org/189
On segunda-feira, 20 de março de 2017 03:47:44 PDT Kai Koehne wrote:
> I don't think this is the case. Every contributor can upload patches with
> new third party code, as long as this is properly documented.
>
> Only maintainers are allowed to approve them though, and if you want to add
> new thi
> -Original Message-
> From: Development [mailto:development-bounces+kai.koehne=qt.io@qt-
> project.org] On Behalf Of Thiago Macieira
> Sent: Sunday, March 19, 2017 8:01 PM
> To: development@qt-project.org
> Subject: [Development] Who's responsible for 3rdparty the
The rules are that only Qt Company people can import 3rdparty code, so I know
I am not responsible.
Who do I assign the bug to?
https://bugreports.qt.io/browse/QTBUG-59586
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
