I have now released version 2.0b6 of cpdb-libs, with a lot of bug fixes,
especially of crashers, and with some changes which needed to apply to ease
sandboxed packaging (Snap, OCI containers, ...) of the backends.
This changes caused slight changes in the API, which could also cause slight
Here are the new api review commits
https://codereview.qt-project.org/c/qt/qtgraphs/+/570029/1
https://codereview.qt-project.org/c/qt/qtgraphs/+/570030/1
I now used api-review-gen script since it's fixed.
From: Sami Varanka
Sent: 14 May 2024 13:42
To:
On Wednesday 19 June 2024 04:32:42 GMT-7 Giuseppe D'Angelo via Development
wrote:
> I wouldn't say "force", but we could certainly check for it. We depend
> on that: we assume that string literals in our headers are UTF-8 encoded.
>
> I it worth it though? Since we're talking about user code,
> Am 19.06.2024 um 10:17 schrieb Eike Ziller via Qt-creator
> :
>
> Hi,
>
> I nominate André Hartmann as the new maintainer of Version Control in Qt
> Creator. His contribution history in Qt Creator goes back to 2011 as well,
> and he regularly worked on improving our version control support
Hi,
On 19/06/2024 11:23, Alexey Edelev via Development wrote:
Hi,
I have a side question for this discussion(raised by Ivan in personal
conversation): Should we also force the -fexec-charset= for the gcc-like
compilers? Currently we use the system default one, which in most cases
is UTF-8.
Following feedback on the Reopens footer, it is now live an can be used in the
commit message with the new behaviour:
* Use Fixes normally to close an issue and as assign a fix version.
* Use the Reopens footer to auto-reopen an issue when a change with the
footer merges. For example,
Hi,
I have a side question for this discussion(raised by Ivan in personal
conversation): Should we also force the -fexec-charset= for the gcc-like
compilers? Currently we use the system default one, which in most cases is
UTF-8.
Regards,
Alexey
Alexey Edelev
Software Engineer
Qt Group
Resent, to fix the cc to the Development mailing list.
> Am 19.06.2024 um 10:17 schrieb Eike Ziller via Qt-creator
> :
>
> Hi,
>
> I nominate André Hartmann as the new maintainer of Version Control in Qt
> Creator. His contribution history in Qt Creator goes back to 2011 as well,
> and he
Hi,
First things first: Users of Qt are unaffected by most of this. They get
a nicer macro to define static logging categories, but everything else
stays the same for them.
Logging categories have been a source of some frustration in Qt itself
because they tend to create symbols that don't
