From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: qt5: Add patch to remove limit on number of HTTP/2 streams (upstream) [ci skip]
Date: Fri, 29 Jul 2022 13:23:12 +0200 [thread overview]
Message-ID: <20220729112312.jz6lgr2YGNbxkdv5m4UHCe9pHjtntjKEdDbLc63r8Uk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38292@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 987 bytes --]
There's a closed pull request on the void-packages repository
qt5: Add patch to remove limit on number of HTTP/2 streams (upstream) [ci skip]
https://github.com/void-linux/void-packages/pull/38292
Description:
#### Testing the changes
- I tested the changes in this PR: **YES**
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
#### Local build testing
- I built this PR locally for my native architecture, x86_64
- I built this PR locally for these architectures:
- x86
This fixes an issue, particularly in the qt5-network package that doesn't let KDE install any themes. This patch was issued upstream: https://code.qt.io/cgit/qt/qtbase.git/commit/?id=46940ca73791e87e
Fixes #38276
prev parent reply other threads:[~2022-07-29 11:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 4:46 [PR PATCH] " z411
2022-07-27 4:59 ` classabbyamp
2022-07-27 4:59 ` classabbyamp
2022-07-27 5:07 ` z411
2022-07-27 5:10 ` classabbyamp
2022-07-27 5:13 ` [PR PATCH] [Updated] " z411
2022-07-27 5:13 ` qt5: " z411
2022-07-27 19:25 ` classabbyamp
2022-07-27 19:26 ` classabbyamp
2022-07-27 21:42 ` [PR PATCH] [Updated] " z411
2022-07-28 2:59 ` z411
2022-07-29 11:23 ` Johnnynator [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=20220729112312.jz6lgr2YGNbxkdv5m4UHCe9pHjtntjKEdDbLc63r8Uk@z \
--to=johnnynator@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).