Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 3/9] xwininfo: Upgrade 1.1.6 -> 1.1.7
Date: Tue,  4 Aug 2026 13:23:29 +0100	[thread overview]
Message-ID: <20260804122335.3094065-3-richard.purdie@linuxfoundation.org> (raw)
In-Reply-To: <20260804122335.3094065-1-richard.purdie@linuxfoundation.org>

Changes:

- xwininfo 1.1.7
- meson: include headers when checking for functions
- meson: Add option to build with meson
- configure: remove local copy of config.rpath
- gitlab CI: drop the ci-fairy check-mr job
- Use stdbool.h
- Fix memory leak in Select_Window
- Fix memory leak in Display_Window_Id
- man page: fix warnings from `mandoc -T lint` and `groff -rCHECKSTYLE=10`
- Improve man page formatting
- Accept --help & --version as aliases to -help & -version
- -help should exit(0) not (1)
- Update xwininfo.man for #2

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
 .../xorg-app/{xwininfo_1.1.6.bb => xwininfo_1.1.7.bb}           | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-graphics/xorg-app/{xwininfo_1.1.6.bb => xwininfo_1.1.7.bb} (81%)

diff --git a/meta/recipes-graphics/xorg-app/xwininfo_1.1.6.bb b/meta/recipes-graphics/xorg-app/xwininfo_1.1.7.bb
similarity index 81%
rename from meta/recipes-graphics/xorg-app/xwininfo_1.1.6.bb
rename to meta/recipes-graphics/xorg-app/xwininfo_1.1.7.bb
index d410f7d5196..6fc49e8729f 100644
--- a/meta/recipes-graphics/xorg-app/xwininfo_1.1.6.bb
+++ b/meta/recipes-graphics/xorg-app/xwininfo_1.1.7.bb
@@ -12,4 +12,4 @@ DEPENDS += "libxext libxmu gettext-native"
 PE = "0"
 
 SRC_URI_EXT = "xz"
-SRC_URI[sha256sum] = "3518897c17448df9ba99ad6d9bb1ca0f17bc0ed7c0fd61281b34ceed29a9253f"
+SRC_URI[sha256sum] = "bee14d594cc86cc59aae1015c1b452a71bf60c304131e2716ca1cf0df733b4ac"


  parent reply	other threads:[~2026-08-04 12:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04 12:23 [PATCH 1/9] libva-utils: 2.23.0 -> 2.24.0 Richard Purdie
2026-08-04 12:23 ` [PATCH 2/9] xvinfo: Upgrade 1.1.5 -> 1.1.6 Richard Purdie
2026-08-04 12:23 ` Richard Purdie [this message]
2026-08-04 12:23 ` [PATCH 4/9] xmodmap: Upgrade 1.0.11 -> 1.0.12 Richard Purdie
2026-08-04 12:36   ` Patchtest results for " patchtest
2026-08-04 12:23 ` [PATCH 5/9] libtool: 2.5.4 -> 2.6.2 Richard Purdie
2026-08-04 12:23 ` [PATCH 6/9] ffmpeg: upgrade 8.1.2 -> 9.0 Richard Purdie
2026-08-04 12:23 ` [PATCH 7/9] libadwaita: upgrade 1.9.2 -> 1.9.3 Richard Purdie
2026-08-04 12:23 ` [PATCH 8/9] python3-cffi: upgrade 2.1.0 -> 2.1.1 Richard Purdie
2026-08-04 12:36   ` Patchtest results for " patchtest
2026-08-04 12:23 ` [PATCH 9/9] python3-pyproject-metadata: upgrade 0.11.0 -> 0.12.1 Richard Purdie
2026-08-04 12:36 ` Patchtest results for [PATCH 1/9] libva-utils: 2.23.0 -> 2.24.0 patchtest
     [not found] ` <18C899AE0F118A3D.1990914@lists.openembedded.org>
2026-08-04 17:00   ` [OE-core] [PATCH 5/9] libtool: 2.5.4 -> 2.6.2 Richard Purdie
     [not found]   ` <18C8A8C4FB56E625.3417489@lists.openembedded.org>
2026-08-04 20:12     ` Richard Purdie
2026-08-04 21:36       ` Jaipaul Cheernam
2026-08-06 21:26         ` Richard Purdie
2026-08-04 21:58       ` Khem Raj

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=20260804122335.3094065-3-richard.purdie@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --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