On Feb 14, 2019, at 1:03 PM, Joe via Development
wrote:
please unsubscribe me from your f. g list
On 14.02.2019 22:20, Joe via Development wrote:
please fuc. g unsubscribeme from your fuk g list i don’t have a
password as i didn’t join but a jerk asshole e put me here
No need to swear.
Summing up the discussion here. It looks like people overall agree that the
pinned dependency approach (option 3) sounds better than what we currently
have. The main concern was CI capacity, but Frederik believes that with enough
storage capacity for build artefacts this will not be worse than w
please fuc. g unsubscribeme from your fuk g list i don’t have a password as i
didn’t join but a jerk asshole e put me here
Sent from my iPad
> On Feb 14, 2019, at 1:03 PM, Joe via Development
> wrote:
>
> please unsubscribe me from your f. g list
>
> Sent from my iPad
>
>>> On Feb 14, 20
please unsubscribe me from your f. g list
Sent from my iPad
> On Feb 14, 2019, at 11:11 AM, drwho wrote:
>
>> On 2019-02-14 5:45 a.m., Pier Luigi Fiorini wrote:
>> Hi,
>>
>> I'd like to know if you have plans of making Qt Quick Templates 2 a public
>> API and allow people to write new contr
On 2019-02-14 5:45 a.m., Pier Luigi Fiorini wrote:
Hi,
I'd like to know if you have plans of making Qt Quick Templates 2 a
public API and allow people to write new controls with C++ without
using a private library.
+1 for this and also for a public api for c++ Qt Quick Controls 2
widgets.
Qt Developers,
Coin production has been successfully updated at Thu Feb 14 15:49:37 UTC 2019.
Changelog updates
https://testresults.qt.io/ci/aakeskim/production_updates/changelog_20190214
Currently cherry-picked in production
https://testresults.qt.io/ci/aakeskim/production_updates/cherrypic
Hi,
I'd like to know if you have plans of making Qt Quick Templates 2 a public
API and allow people to write new controls with C++ without using a private
library.
--
https://liri.io
___
Development mailing list
Development@qt-project.org
https://lists
