From: "WANG Xuerui" <xen0n@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/XS-Parse-Keyword/
Date: Sun, 7 Aug 2022 04:55:21 +0000 (UTC) [thread overview]
Message-ID: <1659847894.bc900312edc64bc8afa4421c505a2edb314995e7.xen0n@gentoo> (raw)
commit: bc900312edc64bc8afa4421c505a2edb314995e7
Author: WANG Xuerui <xen0n <AT> gentoo <DOT> org>
AuthorDate: Sun Aug 7 04:51:34 2022 +0000
Commit: WANG Xuerui <xen0n <AT> gentoo <DOT> org>
CommitDate: Sun Aug 7 04:51:34 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bc900312
dev-perl/XS-Parse-Keyword: keyword 0.240.0 for ~loong
Tests passed on real hardware.
Bug: https://bugs.gentoo.org/863014
Signed-off-by: WANG Xuerui <xen0n <AT> gentoo.org>
dev-perl/XS-Parse-Keyword/XS-Parse-Keyword-0.240.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-perl/XS-Parse-Keyword/XS-Parse-Keyword-0.240.0.ebuild b/dev-perl/XS-Parse-Keyword/XS-Parse-Keyword-0.240.0.ebuild
index bb0087446f45..ebcdf4a18d65 100644
--- a/dev-perl/XS-Parse-Keyword/XS-Parse-Keyword-0.240.0.ebuild
+++ b/dev-perl/XS-Parse-Keyword/XS-Parse-Keyword-0.240.0.ebuild
@@ -9,7 +9,7 @@ inherit perl-module
DESCRIPTION="XS functions to assist in parsing keyword syntax"
SLOT="0"
-KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~ppc ~ppc64 ~riscv ~sparc ~x86"
+KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~ia64 ~loong ~m68k ~ppc ~ppc64 ~riscv ~sparc ~x86"
RDEPEND=""
BDEPEND="${RDEPEND}
next reply other threads:[~2022-08-07 4:55 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-07 4:55 WANG Xuerui [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-02 19:42 [gentoo-commits] repo/gentoo:master commit in: dev-perl/XS-Parse-Keyword/ Sam James
2025-03-01 22:49 Sam James
2025-01-22 5:54 Sam James
2025-01-09 0:08 Sam James
2024-12-14 19:06 Arthur Zamarin
2024-12-09 5:47 Arthur Zamarin
2024-12-07 20:11 Sam James
2024-12-07 3:04 Sam James
2024-12-07 2:44 Sam James
2024-12-06 17:31 Sam James
2024-12-05 18:31 Sam James
2024-12-02 13:15 Jakov Smolić
2024-12-01 18:33 Arthur Zamarin
2024-12-01 18:33 Arthur Zamarin
2024-12-01 18:33 Arthur Zamarin
2024-12-01 18:33 Arthur Zamarin
2024-12-01 18:33 Arthur Zamarin
2024-11-16 23:30 Sam James
2024-11-16 23:27 Sam James
2024-10-14 3:50 Sam James
2024-07-27 12:55 Sam James
2024-07-27 12:00 Sam James
2024-07-07 11:02 Sam James
2024-05-26 21:39 Andreas K. Hüttel
2024-05-01 9:12 Sam James
2024-04-27 6:51 Andreas K. Hüttel
2024-02-28 2:32 Ionen Wolkens
2024-02-28 2:32 Ionen Wolkens
2024-02-28 2:32 Ionen Wolkens
2024-02-28 2:32 Ionen Wolkens
2024-02-12 8:55 Sam James
2023-08-14 7:55 Sam James
2023-07-24 2:57 Sam James
2023-07-20 2:44 Sam James
2023-07-20 2:44 Sam James
2023-06-17 23:35 Sam James
2023-06-03 22:41 Andreas K. Hüttel
2022-09-26 7:31 Michał Górny
2022-09-22 7:46 Michał Górny
2022-09-18 2:55 Akinori Hattori
2022-09-10 8:39 Fabian Groffen
2022-08-13 9:38 Arthur Zamarin
2022-08-06 12:05 James Le Cuirot
2022-08-05 15:28 Arthur Zamarin
2022-08-05 11:56 Arthur Zamarin
2022-08-03 6:32 Yixun Lan
2022-08-02 18:12 Arthur Zamarin
2022-08-02 17:55 Arthur Zamarin
2022-08-02 17:41 Arthur Zamarin
2022-08-02 17:31 Arthur Zamarin
2022-08-02 16:54 Arthur Zamarin
2022-08-02 12:51 Akinori Hattori
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=1659847894.bc900312edc64bc8afa4421c505a2edb314995e7.xen0n@gentoo \
--to=xen0n@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