Marc Mutz via Development wrote:
> Sure, a trivial QWidgets program from the mid-90s may still compile and
> work in Qt 6, but as soon as said program touches Qt container classes,
> it's game over.
A lot of the changes to Qt container classes were either driven by you or at
least praised by you,
Hi all,
SCNR taking the proffered bait:
On 07.11.22 18:51, Edward Welbourne wrote:
> For Qt to remain relevant in the rapidly-evolving C++ landscape, it
> needs to change; but one of its strong selling-points has long been its
> conservatism in API and ABI, that lets working code keep working.
I
Thiago Macieira (7 November 2022 19:22) requested:
> Can you confirm the ED25519 key?
>
> $ ssh-keygen -l -f /home/tjmaciei/.ssh/known_hosts | grep codereview
> 256 SHA256:DwwqNluQyJVkOk+3bFMK6NwWYIGjMnqGP+R0k59e3CY
> [codereview.qt-project.org]:29418 (ED25519)
I can confirm that; it did indeed a
On Sunday, 6 November 2022 22:57:52 PST Jukka Jokiniva via Development wrote:
> The fingerprint for the RSA key sent by the remote host is
>
> SHA256:EPuL0PAbNuXXoye7X93ARF7/XALxA5XNAaE3p6M/L3g.
Can you confirm the ED25519 key?
$ ssh-keygen -l -f /home/tjmaciei/.ssh/known_hosts | grep coderev
Volker Hilsheimer (7 November 2022 16:51) wrote:
> The open question is whether and when we should deprecate such a
> stop-gap 1:1 reimplementations of std functionality. How to deprecate
> is now well documented, but the wiki starts with the process of doing
> so once we concluded that we shall. I
> On 4 Nov 2022, at 16:00, Marc Mutz via Development
> wrote:
>
> Hi,
>
> After getting my head washed by Volker, lemme provide background on
> these two functions.
Thanks for the context, Marc!
> TL;DR: we created real maintenance and porting problems by not removing
> stop-gap functionali
This is now DONE
From: Ville-Pekka Karhu
Sent: Monday, November 7, 2022 08:03
To: Qt development mailing list
Subject: Re: Monthly CI maintenance break - November (Mon 7th Nov 2022)
This maintenance break starts NOW
From: Ville-Pe
On 04.11.22 12:13, Ulf Hermann via Development wrote:
>> One thing I haven't understood about the ordering problem is why we
>> cannot just define our "invalid" values to always be < any valid one and
>> equal to other invalid ones. This way we get at least weak ordering for
>> all our types and we
On Mon, 10 Oct 2022 at 13:13, Hasselmann Mathias
wrote:
>
> I am surprised by the question: "It's non-standard and it's behavior is
> undefined" actually should be enough to avoid such feature.
>
> Actually if a reliable implementation of "#pragma once" would be
> possible, that feature would have
I had a typo on the port number.
Of course the host key update affects the port 28418, where the Gerrit is
running. Not 28419, like I stated earlier.
Sorry for the confusion.
--Jukka
From: Development on behalf of Jukka
Jokiniva via Development
Date: Monday, 7. November 2022 at 9.00
To:
10 matches
Mail list logo
