From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/i2c-tools/
Date: Mon, 21 Feb 2022 03:48:22 +0000 (UTC) [thread overview]
Message-ID: <1645415280.97b8d5b04937840714e14aaed44dd7e2649ac8cd.sam@gentoo> (raw)
commit: 97b8d5b04937840714e14aaed44dd7e2649ac8cd
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Feb 21 03:48:00 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Feb 21 03:48:00 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=97b8d5b0
sys-apps/i2c-tools: Stabilize 4.2 ppc64, #833808
Signed-off-by: Sam James <sam <AT> gentoo.org>
sys-apps/i2c-tools/i2c-tools-4.2.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sys-apps/i2c-tools/i2c-tools-4.2.ebuild b/sys-apps/i2c-tools/i2c-tools-4.2.ebuild
index ad2026877fe8..f922645783a1 100644
--- a/sys-apps/i2c-tools/i2c-tools-4.2.ebuild
+++ b/sys-apps/i2c-tools/i2c-tools-4.2.ebuild
@@ -14,7 +14,7 @@ SRC_URI="https://www.kernel.org/pub/software/utils/${PN}/${P}.tar.xz"
LICENSE="GPL-2"
SLOT="0"
-KEYWORDS="amd64 arm arm64 ~mips ~ppc ~ppc64 ~riscv ~sparc x86"
+KEYWORDS="amd64 arm arm64 ~mips ~ppc ppc64 ~riscv ~sparc x86"
IUSE="perl python"
REQUIRED_USE="python? ( ${PYTHON_REQUIRED_USE} )"
next reply other threads:[~2022-02-21 3:48 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 3:48 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-29 12:15 [gentoo-commits] repo/gentoo:master commit in: sys-apps/i2c-tools/ Sam James
2024-05-28 20:49 Sam James
2024-05-28 20:49 Sam James
2024-05-27 16:14 Joonas Niilola
2024-04-22 17:20 Viorel Munteanu
2024-04-22 16:52 Viorel Munteanu
2024-04-22 16:52 Viorel Munteanu
2023-02-23 13:45 Andrew Ammerlaan
2022-11-15 18:22 Michał Górny
2022-08-28 5:06 WANG Xuerui
2022-05-07 17:50 Arthur Zamarin
2022-05-07 13:20 Jakov Smolić
2022-05-07 10:56 Jakov Smolić
2022-05-07 10:56 Jakov Smolić
2022-05-07 10:05 Arthur Zamarin
2022-05-07 10:04 Arthur Zamarin
2022-05-07 9:58 Arthur Zamarin
2022-05-07 7:19 Sam James
2022-05-07 7:17 Sam James
2022-04-18 20:28 Sam James
2022-02-21 3:48 Sam James
2022-02-01 19:02 Michał Górny
2022-02-01 18:51 Michał Górny
2021-10-31 21:06 Mikle Kolyada
2021-10-28 14:57 Sam James
2021-08-18 0:35 Yixun Lan
2021-06-02 12:50 Sam James
2021-06-02 1:13 Sam James
2021-06-01 15:29 Sam James
2020-12-18 8:19 Mikle Kolyada
2020-10-10 7:58 Mikle Kolyada
2020-03-11 11:36 Mikle Kolyada
2020-03-11 11:36 Mikle Kolyada
2020-02-11 12:25 Michał Górny
2019-12-03 8:30 Mikle Kolyada
2019-11-30 15:40 Mikle Kolyada
2019-09-12 14:28 Michał Górny
2019-08-18 19:50 Mikle Kolyada
2019-02-23 20:57 Mikle Kolyada
2019-02-13 22:00 Mike Frysinger
2019-02-13 22:00 Mike Frysinger
2019-02-13 22:00 Mike Frysinger
2018-12-05 9:17 Mikle Kolyada
2018-12-05 9:09 Mikle Kolyada
2018-04-21 17:33 Mikle Kolyada
2018-03-25 13:29 Mikle Kolyada
2018-03-22 19:58 Mikle Kolyada
2017-12-15 7:33 Jeroen Roovers
2017-12-15 6:59 Jeroen Roovers
2017-05-15 14:19 Manuel Rüger
2017-04-20 16:41 David Seifert
2017-01-15 11:20 Pacho Ramos
2016-12-20 15:30 Tobias Klausmann
2016-10-24 18:13 Markus Meier
2016-10-08 13:56 Pacho Ramos
2016-02-03 9:40 Patrice Clement
2016-02-02 22:24 Mike Frysinger
2016-01-04 10:17 Mike Frysinger
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=1645415280.97b8d5b04937840714e14aaed44dd7e2649ac8cd.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