public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Matt Turner" <mattst88@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/Moose/
Date: Mon,  6 Jul 2020 02:51:05 +0000 (UTC)	[thread overview]
Message-ID: <1594003684.56062b4475a8f6b4e41c4d3fd7d6a4ca9d3f6bc9.mattst88@gentoo> (raw)

commit:     56062b4475a8f6b4e41c4d3fd7d6a4ca9d3f6bc9
Author:     Matt Turner <mattst88 <AT> gentoo <DOT> org>
AuthorDate: Mon Jul  6 02:48:04 2020 +0000
Commit:     Matt Turner <mattst88 <AT> gentoo <DOT> org>
CommitDate: Mon Jul  6 02:48:04 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=56062b44

dev-perl/Moose: Stabilize 2.200.700 ppc, #717060

Signed-off-by: Matt Turner <mattst88 <AT> gentoo.org>

 dev-perl/Moose/Moose-2.200.700.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-perl/Moose/Moose-2.200.700.ebuild b/dev-perl/Moose/Moose-2.200.700.ebuild
index dba9b21bd97..59a382f53b6 100644
--- a/dev-perl/Moose/Moose-2.200.700.ebuild
+++ b/dev-perl/Moose/Moose-2.200.700.ebuild
@@ -11,7 +11,7 @@ inherit perl-module
 DESCRIPTION="A postmodern object system for Perl 5"
 
 SLOT="0"
-KEYWORDS="amd64 ~arm arm64 hppa ~ppc ppc64 sparc x86 ~ppc-aix ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~m68k-mint ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
+KEYWORDS="amd64 ~arm arm64 hppa ppc ppc64 sparc x86 ~ppc-aix ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~m68k-mint ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
 IUSE="test"
 RESTRICT="!test? ( test )"
 


             reply	other threads:[~2020-07-06  2:51 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-06  2:51 Matt Turner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-14  1:50 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Moose/ Sam James
2024-06-09 21:18 Sam James
2024-06-09 20:41 Sam James
2024-05-01  7:10 Sam James
2023-08-27 18:16 Arthur Zamarin
2023-08-27  1:26 Sam James
2023-08-27  1:26 Sam James
2023-08-27  1:26 Sam James
2023-08-27  1:26 Sam James
2023-08-27  1:26 Sam James
2023-08-15  5:18 Sam James
2023-08-03 15:10 Sam James
2023-08-03 15:10 Sam James
2023-08-02 18:30 Arthur Zamarin
2023-08-02 18:27 Arthur Zamarin
2023-08-02 18:27 Arthur Zamarin
2023-07-24  2:57 Sam James
2023-06-20  4:14 Sam James
2022-02-19 19:28 Sam James
2022-02-19 12:08 Arthur Zamarin
2022-02-19  9:28 Arthur Zamarin
2022-02-19  7:27 Arthur Zamarin
2022-02-19  3:41 Sam James
2022-02-19  3:38 Sam James
2021-11-16 20:33 Andreas K. Hüttel
2021-11-16 20:33 Andreas K. Hüttel
2021-09-17  7:51 Yixun Lan
2021-08-26 14:52 Sam James
2021-08-26 14:49 Sam James
2021-08-26  3:00 Sam James
2021-07-26  6:24 Sam James
2021-07-13  4:02 Sam James
2021-07-11 20:51 Sam James
2021-07-10  0:48 Sam James
2021-07-10  0:48 Sam James
2021-07-09  1:36 Sam James
2021-07-08 19:33 Andreas K. Hüttel
2020-12-31  3:25 Andreas K. Hüttel
2020-12-31  3:25 Andreas K. Hüttel
2020-07-20 20:45 Kent Fredric
2020-04-14 15:45 Agostino Sarubbo
2020-04-14 14:03 Agostino Sarubbo
2020-04-12 11:39 Mart Raudsepp
2019-07-28 17:16 Aaron Bauman
2018-10-21  8:39 Fabian Groffen
2018-08-24  6:01 Kent Fredric
2017-11-19  8:36 Kent Fredric
2017-11-09  6:43 Kent Fredric
2017-11-08 20:37 Sergei Trofimovich
2017-11-07 22:52 Sergei Trofimovich
2017-05-29 19:52 Kent Fredric
2017-05-22 11:43 Michael Weber
2017-05-22 10:36 Michael Weber
2017-05-20  8:49 Agostino Sarubbo
2017-03-16  3:13 Kent Fredric
2016-12-26 15:53 Kent Fredric
2016-12-15 15:44 Kent Fredric
2016-03-28 15:33 Andreas Hüttel
2016-02-28 10:01 Patrice Clement
2016-02-06  7:59 Jeroen Roovers
2016-01-24 16:40 Agostino Sarubbo
2015-12-22  0:45 Andreas Hüttel
2015-09-27  8:36 Mikle Kolyada
2015-09-27  5:52 Jeroen Roovers
2015-09-08  5:08 Jeroen Roovers
2015-08-11 20:32 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=1594003684.56062b4475a8f6b4e41c4d3fd7d6a4ca9d3f6bc9.mattst88@gentoo \
    --to=mattst88@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