public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/Test-Differences/
Date: Mon, 24 Jul 2023 03:21:28 +0000 (UTC)	[thread overview]
Message-ID: <1690168870.d760ea23d2f2e57f6334d73ee6ffe2329cef5185.sam@gentoo> (raw)

commit:     d760ea23d2f2e57f6334d73ee6ffe2329cef5185
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Jul 24 03:21:10 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Jul 24 03:21:10 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d760ea23

dev-perl/Test-Differences: Stabilize 0.690.0 ppc, #910944

Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-perl/Test-Differences/Test-Differences-0.690.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-perl/Test-Differences/Test-Differences-0.690.0.ebuild b/dev-perl/Test-Differences/Test-Differences-0.690.0.ebuild
index 6b50cb8a7f54..03545b350e98 100644
--- a/dev-perl/Test-Differences/Test-Differences-0.690.0.ebuild
+++ b/dev-perl/Test-Differences/Test-Differences-0.690.0.ebuild
@@ -10,7 +10,7 @@ inherit perl-module
 DESCRIPTION="Test strings and data structures and show differences if not ok"
 
 SLOT="0"
-KEYWORDS="~alpha amd64 ~arm arm64 ~hppa ~ia64 ~loong ~mips ~ppc ppc64 ~riscv sparc ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x64-solaris"
+KEYWORDS="~alpha amd64 ~arm arm64 ~hppa ~ia64 ~loong ~mips ppc ppc64 ~riscv sparc ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x64-solaris"
 
 RDEPEND="
 	>=dev-perl/Capture-Tiny-0.240.0


             reply	other threads:[~2023-07-24  3:21 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-24  3:21 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-28 18:23 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Test-Differences/ Arthur Zamarin
2024-01-22  9:37 Sam James
2023-12-30  3:07 Sam James
2023-10-29  1:58 Sam James
2023-09-29  0:54 Sam James
2023-08-19 15:37 Arthur Zamarin
2023-08-19  7:23 Sam James
2023-08-19  6:58 Arthur Zamarin
2023-08-19  6:19 Sam James
2023-08-19  6:07 Sam James
2023-08-19  6:07 Sam James
2023-07-24  3:27 Sam James
2023-07-24  3:24 Sam James
2023-07-24  3:19 Sam James
2023-07-24  3:19 Sam James
2023-07-24  3:17 Sam James
2023-07-24  3:17 Sam James
2023-07-08  3:39 Sam James
2023-06-18  4:17 Sam James
2021-12-09 19:46 Andreas K. Hüttel
2021-11-21  4:58 Arthur Zamarin
2021-11-18 21:43 Arthur Zamarin
2021-10-11  6:32 Agostino Sarubbo
2021-10-11  5:20 Sam James
2021-10-11  4:18 Sam James
2021-10-11  3:10 Sam James
2021-08-18 21:46 Andreas K. Hüttel
2020-09-27  8:23 Yixun Lan
2018-10-27 19:04 Fabian Groffen
2018-04-02 18:06 Mart Raudsepp
2018-03-28 17:27 Matt Turner
2017-06-03 20:22 Sergei Trofimovich
2017-03-17 10:42 Agostino Sarubbo
2017-02-04 17:33 Andreas Hüttel
2017-02-03 22:00 Jeroen Roovers
2016-08-04  9:08 Kent Fredric
2016-06-06 14:53 Agostino Sarubbo
2016-06-01 11:52 Tobias Klausmann
2016-03-01 14:43 Andreas Hüttel
2016-02-04 20:51 Tobias Klausmann
2016-01-24  7:20 Jeroen Roovers
2016-01-17 18:24 Agostino Sarubbo
2015-09-27  5:52 Jeroen Roovers
2015-09-07 12:30 Mikle Kolyada

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=1690168870.d760ea23d2f2e57f6334d73ee6ffe2329cef5185.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