From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: x11-misc/picom/
Date: Thu, 20 Apr 2023 04:17:56 +0000 (UTC) [thread overview]
Message-ID: <1681964237.4543d02097ef943abfa7262d4b9268bd81ded3c0.sam@gentoo> (raw)
commit: 4543d02097ef943abfa7262d4b9268bd81ded3c0
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Apr 20 04:16:54 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Apr 20 04:17:17 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4543d020
x11-misc/picom: Stabilize 10.2 amd64, #904567
Signed-off-by: Sam James <sam <AT> gentoo.org>
x11-misc/picom/picom-10.2.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/x11-misc/picom/picom-10.2.ebuild b/x11-misc/picom/picom-10.2.ebuild
index 096c4965a203..bc11b187dee1 100644
--- a/x11-misc/picom/picom-10.2.ebuild
+++ b/x11-misc/picom/picom-10.2.ebuild
@@ -12,7 +12,7 @@ SRC_URI="https://github.com/yshui/picom/archive/v${PV}.tar.gz -> ${P}.tar.gz"
LICENSE="MPL-2.0 MIT"
SLOT="0"
-KEYWORDS="~amd64 ~arm64 ~ppc64 ~riscv ~x86"
+KEYWORDS="amd64 ~arm64 ~ppc64 ~riscv ~x86"
IUSE="+config-file dbus +doc +drm opengl pcre test"
REQUIRED_USE="test? ( dbus )" # avoid "DBus support not compiled in!"
next reply other threads:[~2023-04-20 4:17 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 4:17 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-12 14:59 [gentoo-commits] repo/gentoo:master commit in: x11-misc/picom/ Bernard Cafarelli
2024-11-12 9:13 Bernard Cafarelli
2024-11-12 9:13 Bernard Cafarelli
2024-10-15 7:22 Bernard Cafarelli
2024-10-11 8:50 Bernard Cafarelli
2024-10-04 14:49 Bernard Cafarelli
2024-10-04 14:49 Bernard Cafarelli
2024-10-04 14:49 Bernard Cafarelli
2024-05-29 11:47 Sam James
2024-05-29 6:26 Jakov Smolić
2024-02-23 22:55 Bernard Cafarelli
2024-02-23 22:55 Bernard Cafarelli
2024-02-23 22:55 Bernard Cafarelli
2024-01-30 8:40 Bernard Cafarelli
2024-01-21 19:14 Bernard Cafarelli
2023-11-30 16:17 Bernard Cafarelli
2023-04-20 5:01 Sam James
2022-12-18 19:12 Bernard Cafarelli
2022-12-18 19:12 Bernard Cafarelli
2022-12-17 23:22 Bernard Cafarelli
2022-12-17 23:22 Bernard Cafarelli
2022-08-20 15:54 Arthur Zamarin
2022-06-12 8:28 Agostino Sarubbo
2022-06-10 7:11 Agostino Sarubbo
2022-02-14 8:07 Bernard Cafarelli
2022-01-28 22:53 Bernard Cafarelli
2022-01-28 22:53 Bernard Cafarelli
2022-01-11 2:23 Georgy Yakovlev
2021-10-10 22:14 Marek Szuba
2021-06-12 5:50 Sam James
2021-06-12 5:47 Sam James
2021-06-07 23:10 Sam James
2021-06-07 23:10 Sam James
2021-06-07 16:44 Sam James
2021-04-22 10:32 Bernard Cafarelli
2021-04-22 10:32 Bernard Cafarelli
2021-03-09 19:19 Bernard Cafarelli
2021-03-09 19:19 Bernard Cafarelli
2021-01-02 0:35 Sam James
2020-10-24 9:25 Bernard Cafarelli
2020-09-16 11:32 Bernard Cafarelli
2020-06-06 10:56 Georgy Yakovlev
2020-05-08 16:00 Bernard Cafarelli
2020-03-06 12:32 Agostino Sarubbo
2020-03-06 11:35 Agostino Sarubbo
2020-01-09 20:01 Bernard Cafarelli
2019-12-16 10:26 Bernard Cafarelli
2019-12-10 12:22 Bernard Cafarelli
2019-12-09 13:50 Bernard Cafarelli
2019-12-07 8:09 Bernard Cafarelli
2019-12-06 21:33 Bernard Cafarelli
2019-12-06 12:18 Bernard Cafarelli
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=1681964237.4543d02097ef943abfa7262d4b9268bd81ded3c0.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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