public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/Perl-Critic/
Date: Sun, 25 Feb 2018 22:05:36 +0000 (UTC)	[thread overview]
Message-ID: <1519596313.30861d50b0baef8aaccc9fdebb86abf3796fdfbb.slyfox@gentoo> (raw)

commit:     30861d50b0baef8aaccc9fdebb86abf3796fdfbb
Author:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 25 22:05:13 2018 +0000
Commit:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sun Feb 25 22:05:13 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=30861d50

dev-perl/Perl-Critic: stable 1.130.0 for ppc, bug #648584

Package-Manager: Portage-2.3.24, Repoman-2.3.6
RepoMan-Options: --include-arches="ppc"

 dev-perl/Perl-Critic/Perl-Critic-1.130.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-perl/Perl-Critic/Perl-Critic-1.130.0.ebuild b/dev-perl/Perl-Critic/Perl-Critic-1.130.0.ebuild
index b5203caa444..3bc0106863a 100644
--- a/dev-perl/Perl-Critic/Perl-Critic-1.130.0.ebuild
+++ b/dev-perl/Perl-Critic/Perl-Critic-1.130.0.ebuild
@@ -10,7 +10,7 @@ inherit perl-module elisp-common
 DESCRIPTION="Critique Perl source code for best-practices"
 
 SLOT="0"
-KEYWORDS="~alpha amd64 ~ppc ~ppc64 x86 ~amd64-linux ~x86-linux ~ppc-macos ~x86-macos ~sparc-solaris"
+KEYWORDS="~alpha amd64 ppc ~ppc64 x86 ~amd64-linux ~x86-linux ~ppc-macos ~x86-macos ~sparc-solaris"
 IUSE="test minimal examples emacs"
 SITEFILE="50${PN}-gentoo.el"
 RDEPEND="


             reply	other threads:[~2018-02-25 22:05 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-25 22:05 Sergei Trofimovich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-24 16:25 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Perl-Critic/ Matt Turner
2024-12-02 13:15 Jakov Smolić
2024-12-01 19:02 Arthur Zamarin
2024-10-24 10:23 Sam James
2024-09-21 19:58 Arthur Zamarin
2024-07-07  6:23 Sam James
2024-07-07  6:10 Sam James
2024-05-01  8:23 Sam James
2024-02-03 19:09 Sam James
2024-02-03 10:56 Sam James
2024-02-02  5:13 Sam James
2023-11-30 15:59 Ionen Wolkens
2023-11-13  4:35 Sam James
2023-10-16 16:34 Joonas Niilola
2023-09-28  1:57 Sam James
2023-08-26  5:04 Sam James
2023-08-24 21:25 Sam James
2023-08-24 21:25 Sam James
2023-07-04  5:22 WANG Xuerui
2023-06-24  8:51 Jakov Smolić
2023-06-24  4:12 Sam James
2023-06-24  3:59 Sam James
2023-06-24  3:56 Sam James
2023-06-19  3:26 Sam James
2021-11-25  1:35 Andreas K. Hüttel
2021-08-03 11:08 Sam James
2021-07-28  1:58 Sam James
2021-07-24 20:23 Matt Turner
2021-07-17 19:29 Andreas K. Hüttel
2021-05-15  2:44 Sam James
2021-05-10 13:12 Sam James
2021-05-09 16:54 Andreas K. Hüttel
2018-03-22  6:58 Kent Fredric
2018-03-05 17:13 Tobias Klausmann
2018-02-24  8:07 Jason Zaman
2017-12-23  0:23 Kent Fredric
2016-08-05  1:30 Kent Fredric
2016-07-06 22:54 Andreas Hüttel
2016-05-25 23:27 Matt Turner
2016-05-25 23:27 Matt Turner
2016-05-13 10:12 Agostino Sarubbo
2016-04-15 19:56 Andreas Hüttel
2016-03-19 22:42 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=1519596313.30861d50b0baef8aaccc9fdebb86abf3796fdfbb.slyfox@gentoo \
    --to=slyfox@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