From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/Clone/
Date: Tue, 4 May 2021 19:16:48 +0000 (UTC) [thread overview]
Message-ID: <1620155753.b8de793171f24b6475ffa87fab5296f7ad6fee29.sam@gentoo> (raw)
commit: b8de793171f24b6475ffa87fab5296f7ad6fee29
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue May 4 19:15:53 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue May 4 19:15:53 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b8de7931
dev-perl/Clone: Stabilize 0.450.0 ppc64, #787776
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-perl/Clone/Clone-0.450.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-perl/Clone/Clone-0.450.0.ebuild b/dev-perl/Clone/Clone-0.450.0.ebuild
index 2802c696425..bdd7d452745 100644
--- a/dev-perl/Clone/Clone-0.450.0.ebuild
+++ b/dev-perl/Clone/Clone-0.450.0.ebuild
@@ -10,7 +10,7 @@ inherit perl-module
DESCRIPTION="Recursively copy Perl datatypes"
SLOT="0"
-KEYWORDS="~alpha ~amd64 arm ~arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~riscv ~sparc ~x86 ~x64-macos"
+KEYWORDS="~alpha ~amd64 arm ~arm64 ~hppa ~ia64 ~mips ~ppc ppc64 ~riscv ~sparc ~x86 ~x64-macos"
IUSE="test"
RESTRICT="!test? ( test )"
next reply other threads:[~2021-05-04 19:16 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 19:16 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-14 3:39 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Clone/ Sam James
2024-11-14 3:21 Sam James
2024-11-14 2:49 Sam James
2024-10-11 3:39 Sam James
2023-03-04 22:30 Jakov Smolić
2023-03-04 17:28 Arthur Zamarin
2023-03-04 14:40 Arthur Zamarin
2023-03-04 13:22 Arthur Zamarin
2023-03-04 13:22 Arthur Zamarin
2023-03-04 13:17 Arthur Zamarin
2023-03-04 13:17 Arthur Zamarin
2023-03-04 13:13 Arthur Zamarin
2022-11-19 4:50 WANG Xuerui
2022-11-18 4:52 Sam James
2022-11-18 4:52 Sam James
2022-04-25 15:06 Sam James
2021-10-11 21:27 Andreas K. Hüttel
2021-05-06 10:01 Sam James
2021-05-06 7:22 Sergei Trofimovich
2021-05-04 22:25 Sam James
2021-05-04 22:24 Sam James
2021-05-04 19:16 Sam James
2021-05-04 19:13 Sam James
2020-12-27 14:42 Fabian Groffen
2020-11-28 9:57 Sam James
2020-10-22 5:11 Joshua Kinard
2020-09-26 19:44 Matt Turner
2020-09-03 4:26 Yixun Lan
2020-07-09 21:58 Sam James
2020-07-07 6:58 Sergei Trofimovich
2020-07-06 16:44 Sergei Trofimovich
2020-07-05 11:37 Sergei Trofimovich
2020-07-05 11:35 Sergei Trofimovich
2020-07-04 8:56 Sergei Trofimovich
2020-06-26 13:42 Kent Fredric
2019-07-28 18:31 Aaron Bauman
2018-10-27 15:19 Fabian Groffen
2018-04-02 18:06 Mart Raudsepp
2017-08-27 15:42 Mikle Kolyada
2017-08-27 15:41 Mikle Kolyada
2017-06-10 15:10 Agostino Sarubbo
2017-05-28 6:43 Markus Meier
2017-05-22 13:25 Tobias Klausmann
2017-05-22 11:40 Agostino Sarubbo
2017-05-22 1:19 Michael Weber
2017-05-20 9:34 Agostino Sarubbo
2017-05-20 8:49 Agostino Sarubbo
2017-04-07 19:10 Kent Fredric
2016-01-24 12:11 Andreas Hüttel
2016-01-24 7:39 Jeroen Roovers
2016-01-17 19:03 Mikle Kolyada
2016-01-17 13:32 Mikle Kolyada
2016-01-10 10:34 Agostino Sarubbo
2016-01-09 16:12 Markus Meier
2016-01-09 6:43 Agostino Sarubbo
2016-01-02 18:53 Agostino Sarubbo
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=1620155753.b8de793171f24b6475ffa87fab5296f7ad6fee29.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