On Fri, 2019-11-01 at 13:24 +0100, Martin Jansa wrote:
> This patch is already included in 5.13.2 upgrade (ready in zeus-next
> and master-next branches), so you don't need to do anything.
Okay, that's great!
> Otherwise like Khem says, submit the change for meta-qt5 repository
> like any other
This patch is already included in 5.13.2 upgrade (ready in zeus-next and
master-next branches), so you don't need to do anything.
Otherwise like Khem says, submit the change for meta-qt5 repository like
any other layer.
The meta-qt5/qt* repositories are used to maintain the patches, but usually
On Fri, Nov 1, 2019 at 3:02 AM Tanu Kaskinen wrote:
> Hi all!
>
> The meta-qt5 readme says that contributions should be made by forking
> the meta-qt5 repository on GitHub, but when I look at the qtwebengine
> recipe, it looks like patches are pulled from
>
Hi all!
The meta-qt5 readme says that contributions should be made by forking
the meta-qt5 repository on GitHub, but when I look at the qtwebengine
recipe, it looks like patches are pulled from
https://github.com/meta-qt5/qtwebengine-chromium, and that repository
looks like the patches are kept
