From: "Eilís 'pidge' Ní Fhlannagáin" <pidge@baylibre.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] wayland/weston upgrades
Date: Thu, 15 Jun 2023 20:20:37 +0100 [thread overview]
Message-ID: <cover.1686856412.git.pidge@baylibre.com> (raw)
Nothing really surprising here, except we should note that launcher-logind is
being depreciated so some thought on how that is dealt with will need to occur.
Eilís 'pidge' Ní Fhlannagáin (3):
wayland-utils: upgrade 1.1.0 -> 1.2.0
weston: Upgrade 11.0.1 -> 12.0.1
xwayland: Upgrade 23.1.1 -> 23.1.2
...ayland-info-Fix-build-without-libdrm.patch | 42 -------------------
...-utils_1.1.0.bb => wayland-utils_1.2.0.bb} | 3 +-
.../{weston_11.0.1.bb => weston_12.0.1.bb} | 10 +++--
...{xwayland_23.1.1.bb => xwayland_23.1.2.bb} | 2 +-
4 files changed, 9 insertions(+), 48 deletions(-)
delete mode 100644 meta/recipes-graphics/wayland/files/0001-wayland-info-Fix-build-without-libdrm.patch
rename meta/recipes-graphics/wayland/{wayland-utils_1.1.0.bb => wayland-utils_1.2.0.bb} (82%)
rename meta/recipes-graphics/wayland/{weston_11.0.1.bb => weston_12.0.1.bb} (92%)
rename meta/recipes-graphics/xwayland/{xwayland_23.1.1.bb => xwayland_23.1.2.bb} (95%)
--
2.34.1
next reply other threads:[~2023-06-15 19:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 19:20 Eilís 'pidge' Ní Fhlannagáin [this message]
2023-06-15 19:20 ` [PATCH 1/3] wayland-utils: upgrade 1.1.0 -> 1.2.0 Eilís 'pidge' Ní Fhlannagáin
2023-06-15 19:20 ` [PATCH 2/3] weston: Upgrade 11.0.1 -> 12.0.1 Eilís 'pidge' Ní Fhlannagáin
2023-06-15 19:52 ` [OE-core] " Alexander Kanavin
2023-06-15 19:20 ` [PATCH 3/3] xwayland: Upgrade 23.1.1 -> 23.1.2 Eilís 'pidge' Ní Fhlannagáin
2023-06-16 7:31 ` [OE-core] [PATCH 0/3] wayland/weston upgrades Richard Purdie
2023-06-16 12:06 ` Eilís 'pidge' Ní Fhlannagáin
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=cover.1686856412.git.pidge@baylibre.com \
--to=pidge@baylibre.com \
--cc=openembedded-core@lists.openembedded.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