On 15.03.19 14:53, Paul Wicking wrote:
> On 3/15/19 2:38 PM, Edward Welbourne wrote:
>> Please report a QTQAINFRA bug and assign to Frederik (who originally
>> proposed this tool).
>>
> ...or just fix it: https://git.qt.io/qtqa/jira-bug-closer
>
what is this?
this doesn't seem to be under codere
On Friday, 15 March 2019 11:12:30 PDT Thiago Macieira wrote:
> On Friday, 15 March 2019 11:09:20 PDT Matthew Woehlke wrote:
> > (Note: Another solution is to redefine QT_UNICODE_LITERAL_II to `u ##
> > str`, but that's SIC.)
>
> And doesn't help, because you *can* write
>
> QStringLiteral("
Integrations and Provisionings
* qt5 5.12, 5.13 and dev are healthy, finally after
https://testresults.qt.io/coin/integration/qt/qt5/tasks/1552656661
Merges
Please check
https://codereview.qt-project.org/#/q/owner:%22Qt+Forward+Merge+Bot+%253Cqt_forward_merge_bot%2540qt-project.org%253E%22++st
On Friday, 15 March 2019 11:09:20 PDT Matthew Woehlke wrote:
> (Note: Another solution is to redefine QT_UNICODE_LITERAL_II to `u ##
> str`, but that's SIC.)
And doesn't help, because you *can* write
QStringLiteral("a" "b" "c")
--
Thiago Macieira - thiago.macieira (AT) intel.com
Softw
On 15/03/2019 08.27, Giuseppe D'Angelo via Development wrote:
> Il 14/03/19 22:48, Thiago Macieira ha scritto:
>> For
>>
>> char16_t text1[] = u"" "\u0102";
>>
>> It produces, without /utf-8 (seehttps://msvc.godbolt.org/z/EvtKzq):
>>
>> ?text1@@3PA_SA DB '?', 00H, 00H, 00H ; t
On Friday, 15 March 2019 05:27:09 PDT Giuseppe D'Angelo via Development wrote:
> The mapping of \u escape sequences to the execution character set
> happens before string literal concatenation (translation phases 5/6).
> But AFAIU the mapping is purely symbolic, and has nothing to do with any
> act
Pendleton, Corey (Friday, March 15, 2019 at 9:51 AM)
>>> I am having https errors accessing both forum.qt.io and wiki.qt.io.
Jason H (Friday, March 15, 2019 8:54 AM)
>> I, in US/East Coast, am not.
Pendleton, Corey (15 March 2019 14:56)
> And now it’s working again. This may be an internal IT is
Am 15.03.2019 um 14:38 schrieb Edward Welbourne:
> Robert Loehning (15 March 2019 14:05) wrote:
>> imagine the following situation:
>> 1. Bug in 5.13 is reported
>> 2. Patch with "Fixes: " is merged to 5.13 branch
>> 3. Gerrit Bot closes the report with "Fix Version 5.13".
>> 4. Reporter tests 5.13
And now it’s working again. This may be an internal IT issue for me. I will
reach out to them, but just wanted to let someone know.
Sorry for the inconvenience.
Corey
From: Jason H
Sent: Friday, March 15, 2019 8:54 AM
To: Pendleton, Corey
Cc: development@qt-project.org
Subject: Re: [Development
I, in US/East Coast, am not.
Sent: Friday, March 15, 2019 at 9:51 AM
From: "Pendleton, Corey"
To: "development@qt-project.org"
Subject: [Development] Website Issues
To Whom It May Concern,
I am having https errors accessing both forum.qt.io and wiki.qt.io.
Thanks!
Corey
CONFID
On 3/15/19 2:38 PM, Edward Welbourne wrote:
> Please report a QTQAINFRA bug and assign to Frederik (who originally
> proposed this tool).
>
...or just fix it: https://git.qt.io/qtqa/jira-bug-closer
P.
___
Development mailing list
Development@qt-project.
To Whom It May Concern,
I am having https errors accessing both forum.qt.io and wiki.qt.io.
Thanks!
Corey
CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of
the intended recipient(s) and contain information that may be Garmin
confid
Robert Loehning (15 March 2019 14:05) wrote:
> imagine the following situation:
> 1. Bug in 5.13 is reported
> 2. Patch with "Fixes: " is merged to 5.13 branch
> 3. Gerrit Bot closes the report with "Fix Version 5.13".
> 4. Reporter tests 5.13 branch, fix failed, reopens report
> 5. Patch is merged
Edward Welbourne (perjantai 15. maaliskuuta 2019 11.49) wrote
>> Yesterday I updated the remaining reviews (and closed one as fatuous), to
>> pick up changes folk have made in the interval. I note, with some concern,
>> that there have been quite a lot of changes to qtbase's API that weren't
>> re
Hi *,
imagine the following situation:
1. Bug in 5.13 is reported
2. Patch with "Fixes: " is merged to 5.13 branch
3. Gerrit Bot closes the report with "Fix Version 5.13".
4. Reporter tests 5.13 branch, fix failed, reopens report
5. Patch is merged to dev branch
6. Gerrit Bot finds the patch in de
> -Original Message-
> From: Edward Welbourne
> Sent: perjantai 15. maaliskuuta 2019 11.49
> To: development@qt-project.org
> Cc: Jani Heikkinen
> Subject: Re: HEADS-UP: Qt 5.13 API review
>
> Yesterday I updated the remaining reviews (and closed one as fatuous), to
> pick up changes fol
Il 14/03/19 22:48, Thiago Macieira ha scritto:
For
char16_t text1[] = u"" "\u0102";
It produces, without /utf-8 (seehttps://msvc.godbolt.org/z/EvtKzq):
?text1@@3PA_SA DB '?', 00H, 00H, 00H; text1
And with /utf-8:
?text1@@3PA_SA DB 0c4H, 00H, 01aH, ' ', 00H, 00H
Hi All,
We have finally released Qt 5.12.2 today, see more information from
https://blog.qt.io/blog/2019/03/15/qt-5-12-2-released/
Big thanks to everyone involved!
br,
Jani Heikkinen
Release Manager
___
Development mailing list
Development@qt-project
Jani Heikkinen (1 February 2019 13:53) wrote:
>>> Feature freeze for Qt 5.13 is now in effect and branching from 'dev' to
>>> '5.13' is complete.
Edward Welbourne (Monday, February 4, 2019 1:38 PM)
>> and that means it's time to review changes to all our APIs, please see
>> https://codereview.qt
19 matches
Mail list logo
