Hi!
On Thu, 10 Dec 2020 at 13:13, Kai Köhne wrote:
>
>
> > -Original Message-
> > From: Development On Behalf Of
> > Thiago Macieira
> > Sent: Thursday, December 10, 2020 3:48 PM
> > To: development@qt-project.org
> > Subject: Re: [Development] Qt 6 co-installability with Qt 5
> >
> > O
> -Original Message-
> From: Development On Behalf Of
> Thiago Macieira
> Sent: Thursday, December 10, 2020 3:48 PM
> To: development@qt-project.org
> Subject: Re: [Development] Qt 6 co-installability with Qt 5
>
> On Wednesday, 9 December 2020 23:24:00 PST Kai Köhne wrote:
> > Consiste
On Wednesday, 9 December 2020 23:24:00 PST Kai Köhne wrote:
> Consistency is important, but is it really so that people struggle with
> realizing that 'linguist' is 'linguist6' in their local Linux installation?
>
> If this is really a problem we can consider just mentioning both names in
> the do
Hi all!
We’ll have our scheduled maintenance break on next Monday (14th of Dec). We’ll
begin our work at 8:00 EET and you can prepare for 3 hours of CI not working.
Br,
VP
___
Development mailing list
Development@qt-project.org
https://lists.qt-pr
> On 9 Dec 2020, at 21:34, Thiago Macieira wrote:
>
> They've finally fixed the thread_local problem
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83562
>
> So when can we require a fixed version of GCC or require Clang for MinGW?
Good question. Is there a chance to move over to one of those
> On 9 Dec 2020, at 18:49, Thiago Macieira wrote:
>
> On Wednesday, 9 December 2020 02:00:29 PST Benjamin TERRIER wrote:
>> Back to the topic, wouldn't it be acceptable to break BC before 6.2 release?
>> I mean Qt 6 isn't really complete until 6.2, so if a break is required it
>> kind of makes se
