From: "Andreas Hüttel" <dilfridge@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/PPIx-Regexp/
Date: Fri, 27 May 2016 21:49:02 +0000 (UTC) [thread overview]
Message-ID: <1464385136.4e65cded7431692d2192a3ed984b0dfcec072c2e.dilfridge@gentoo> (raw)
commit: 4e65cded7431692d2192a3ed984b0dfcec072c2e
Author: Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
AuthorDate: Fri May 27 21:38:56 2016 +0000
Commit: Andreas Hüttel <dilfridge <AT> gentoo <DOT> org>
CommitDate: Fri May 27 21:38:56 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4e65cded
dev-perl/PPIx-Regexp: Retroactively stable for ppc/x86 (ALLARCHES), bug 580978
Package-Manager: portage-2.3.0_rc1
dev-perl/PPIx-Regexp/PPIx-Regexp-0.48.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-perl/PPIx-Regexp/PPIx-Regexp-0.48.0.ebuild b/dev-perl/PPIx-Regexp/PPIx-Regexp-0.48.0.ebuild
index bffab4a..8aed969 100644
--- a/dev-perl/PPIx-Regexp/PPIx-Regexp-0.48.0.ebuild
+++ b/dev-perl/PPIx-Regexp/PPIx-Regexp-0.48.0.ebuild
@@ -11,7 +11,7 @@ inherit perl-module
DESCRIPTION="Represent a regular expression of some sort"
SLOT="0"
-KEYWORDS="alpha amd64 ~ppc ~ppc64 ~x86"
+KEYWORDS="alpha amd64 ppc ~ppc64 x86"
IUSE="test examples"
RDEPEND="
next reply other threads:[~2016-05-27 21:49 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 21:49 Andreas Hüttel [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-06 6:20 [gentoo-commits] repo/gentoo:master commit in: dev-perl/PPIx-Regexp/ Sam James
2025-10-06 6:20 Sam James
2025-07-12 14:24 Arthur Zamarin
2025-07-12 3:51 Sam James
2025-07-12 3:11 Sam James
2025-06-06 3:44 Sam James
2024-09-21 19:58 Arthur Zamarin
2024-07-07 6:23 Sam James
2024-07-07 6:10 Sam James
2023-12-01 3:30 Sam James
2023-10-16 16:34 Joonas Niilola
2023-09-28 1:57 Sam James
2023-09-28 0:21 Sam James
2023-08-19 15:37 Arthur Zamarin
2023-07-04 5:22 WANG Xuerui
2023-06-24 3:59 Sam James
2023-06-24 3:56 Sam James
2023-06-24 3:56 Sam James
2023-06-19 0:47 Sam James
2022-02-19 7:19 Arthur Zamarin
2022-02-19 3:41 Sam James
2022-02-19 3:06 Sam James
2021-11-27 14:09 Andreas K. Hüttel
2021-11-27 14:09 Andreas K. Hüttel
2021-05-09 16:54 Andreas K. Hüttel
2020-07-18 10:53 Kent Fredric
2020-07-18 10:53 Kent Fredric
2020-07-18 7:04 Kent Fredric
2019-07-25 6:48 Kent Fredric
2018-10-27 12:45 Fabian Groffen
2018-09-01 19:01 Thomas Deutschmann
2018-08-20 4:40 Matt Turner
2018-07-27 7:08 Sergei Trofimovich
2018-07-24 0:12 Mikle Kolyada
2017-12-26 8:48 Kent Fredric
2017-02-19 15:22 Kent Fredric
2016-05-27 21:49 Andreas Hüttel
2016-05-25 23:27 Matt Turner
2016-05-13 10:12 Agostino Sarubbo
2016-04-07 23:08 Andreas Hüttel
2016-04-07 23:07 Andreas Hüttel
2016-03-16 14:09 Agostino Sarubbo
2016-02-03 14:36 Tobias Klausmann
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=1464385136.4e65cded7431692d2192a3ed984b0dfcec072c2e.dilfridge@gentoo \
--to=dilfridge@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