From: 0x5c <0x5c@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: picom: update to 12.3.
Date: Fri, 18 Oct 2024 02:17:02 +0200 [thread overview]
Message-ID: <20241018001702.614C6220D1@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-52638@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 476 bytes --]
New comment by 0x5c on void-packages repository
https://github.com/void-linux/void-packages/pull/52638#issuecomment-2420912754
Comment:
The update as-is should be usable, and the arm32 patch from upstream does indeed fix compilation. However, I've talked with upstream and they're planning to release another patch release in about a week, so I'll be waiting for that.
In the mean time, if anyone uses picom on arm32 (`armv6l`/`armv7l`, musl or not), testing is welcome.
next prev parent reply other threads:[~2024-10-18 0:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 16:19 [PR PATCH] " 0x5c
2024-10-15 7:53 ` pondichys
2024-10-16 18:53 ` [PR PATCH] [Updated] " 0x5c
2024-10-18 0:17 ` 0x5c [this message]
2024-10-30 2:48 ` [PR PATCH] [Merged]: " classabbyamp
2024-10-21 10:50 [PR PATCH] " dataCobra
2024-10-21 14:57 ` classabbyamp
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=20241018001702.614C6220D1@inbox.vuxu.org \
--to=0x5c@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).