From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 01/31] package/qt5: bump version to 5.15.2
Date: Sun, 13 Dec 2020 11:41:25 +0100 [thread overview]
Message-ID: <20201213114125.4b3ef431@gmx.net> (raw)
In-Reply-To: <87im96yq44.fsf@dell.be.48ers.dk>
Hello Peter,
On Sun, 13 Dec 2020 11:09:15 +0100, Peter Korsgaard <peter@korsgaard.com> wrote:
> >>>>> "Peter" == Peter Seiderer <ps.report@gmx.net> writes:
>
> > qt5base:
> > - header.BSD was remove with commit 'Remove license header
> > templates from qtbase' ([1])
>
> > qt5tools:
> > - rebase 0001-Disable-designer-tool-fixes-configure-error.patch
>
> > qt5webengine:
> > - update 3rdparty license info
>
> > [1] https://code.qt.io/cgit/qt/qtbase.git/commit/?id=9ac8b9c92eb01bf755995669ecd7ab3acf21dd7d
>
> > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
>
> Is there a list of fixes somewhere? Should this be backported to
> 2020.11.x?
>
According to [1] 176 bug fixes ([2]), more details (links to the per module
changes) on the changes page [3]...
Regards,
Peter
[1] https://www.qt.io/blog/qt-5.15.2-released
[2] https://bugreports.qt.io/issues/?filter=22659
[3] https://wiki.qt.io/Qt_5.15.2_Change_Files
prev parent reply other threads:[~2020-12-13 10:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 21:12 [Buildroot] [PATCH v1 01/31] package/qt5: bump version to 5.15.2 Peter Seiderer
2020-11-21 21:12 ` [Buildroot] [PATCH v1 02/31] package/qt53d: format hash file according to two spaces guideline Peter Seiderer
2020-11-21 21:12 ` [Buildroot] [PATCH v1 03/31] package/qt5base: " Peter Seiderer
2020-11-21 21:12 ` [Buildroot] [PATCH v1 04/31] package/qt5charts: " Peter Seiderer
2020-11-21 21:12 ` [Buildroot] [PATCH v1 05/31] package/qt5connectivity: " Peter Seiderer
2020-11-21 21:12 ` [Buildroot] [PATCH v1 06/31] package/qt5declarative: " Peter Seiderer
2020-11-21 21:12 ` [Buildroot] [PATCH v1 07/31] package/qt5enginio: " Peter Seiderer
2020-11-21 21:12 ` [Buildroot] [PATCH v1 08/31] package/qt5graphicaleffects: " Peter Seiderer
2020-11-21 21:12 ` [Buildroot] [PATCH v1 09/31] package/qt5imageformats: " Peter Seiderer
2020-11-21 21:12 ` [Buildroot] [PATCH v1 10/31] package/qt5location: " Peter Seiderer
2020-11-21 21:12 ` [Buildroot] [PATCH v1 11/31] package/qt5multimedia: " Peter Seiderer
2020-11-21 21:12 ` [Buildroot] [PATCH v1 12/31] package/qt5quickcontrols: " Peter Seiderer
2020-11-21 21:12 ` [Buildroot] [PATCH v1 13/31] package/qt5quickcontrols2: " Peter Seiderer
2020-11-21 21:12 ` [Buildroot] [PATCH v1 14/31] package/qt5script: " Peter Seiderer
2020-11-21 21:12 ` [Buildroot] [PATCH v1 15/31] package/qt5scxml: " Peter Seiderer
2020-11-21 21:12 ` [Buildroot] [PATCH v1 16/31] package/qt5sensors: " Peter Seiderer
2020-11-21 21:12 ` [Buildroot] [PATCH v1 17/31] package/qt5serialbus: " Peter Seiderer
2020-11-21 21:12 ` [Buildroot] [PATCH v1 18/31] package/qt5serialport: " Peter Seiderer
2020-11-21 21:12 ` [Buildroot] [PATCH v1 19/31] package/qt5svg: " Peter Seiderer
2020-11-21 21:12 ` [Buildroot] [PATCH v1 20/31] package/qt5tools: " Peter Seiderer
2020-12-10 20:18 ` [Buildroot] [PATCH v1 01/31] package/qt5: bump version to 5.15.2 Thomas Petazzoni
2020-12-10 21:46 ` Peter Seiderer
2020-12-10 21:11 ` Thomas Petazzoni
2020-12-13 10:09 ` Peter Korsgaard
2020-12-13 10:41 ` Peter Seiderer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201213114125.4b3ef431@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox