public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jeroen Roovers" <jer@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/Try-Tiny/
Date: Sun, 24 Jan 2016 07:39:15 +0000 (UTC)	[thread overview]
Message-ID: <1453621133.902d2d177a32fdf19f4b8d51074c2940aacb4ffc.jer@gentoo> (raw)

commit:     902d2d177a32fdf19f4b8d51074c2940aacb4ffc
Author:     Jeroen Roovers <jer <AT> gentoo <DOT> org>
AuthorDate: Sun Jan 24 07:33:14 2016 +0000
Commit:     Jeroen Roovers <jer <AT> gentoo <DOT> org>
CommitDate: Sun Jan 24 07:38:53 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=902d2d17

dev-perl/Try-Tiny: Stable for HPPA (bug #570368).

Package-Manager: portage-2.2.27
RepoMan-Options: --ignore-arches

 dev-perl/Try-Tiny/Try-Tiny-0.220.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-perl/Try-Tiny/Try-Tiny-0.220.0.ebuild b/dev-perl/Try-Tiny/Try-Tiny-0.220.0.ebuild
index 5eadd05..bea919b 100644
--- a/dev-perl/Try-Tiny/Try-Tiny-0.220.0.ebuild
+++ b/dev-perl/Try-Tiny/Try-Tiny-0.220.0.ebuild
@@ -12,7 +12,7 @@ DESCRIPTION="Minimal try/catch with proper localization of $@"
 
 LICENSE="MIT"
 SLOT="0"
-KEYWORDS="alpha amd64 arm ~arm64 ~hppa ia64 ~m68k ~mips ppc ppc64 ~s390 ~sh sparc x86 ~ppc-aix ~x86-fbsd ~x86-freebsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~x86-solaris"
+KEYWORDS="alpha amd64 arm ~arm64 hppa ia64 ~m68k ~mips ppc ppc64 ~s390 ~sh sparc x86 ~ppc-aix ~x86-fbsd ~x86-freebsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~x86-solaris"
 IUSE="test"
 
 RDEPEND="


             reply	other threads:[~2016-01-24  7:39 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-24  7:39 Jeroen Roovers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-02-22  9:30 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Try-Tiny/ Arthur Zamarin
2022-02-19 12:31 Arthur Zamarin
2022-02-19 12:09 Arthur Zamarin
2022-02-19  9:59 Arthur Zamarin
2022-02-19  8:27 Arthur Zamarin
2022-02-19  7:33 Arthur Zamarin
2022-02-19  7:00 Arthur Zamarin
2021-12-11  4:33 Andreas K. Hüttel
2021-09-29 20:03 Andreas K. Hüttel
2020-12-27 16:19 Fabian Groffen
2020-07-24 18:58 Fabian Groffen
2020-07-18  3:42 Kent Fredric
2020-04-15 15:40 Kent Fredric
2019-05-04 19:08 Andreas K. Hüttel
2018-12-22 10:37 Mikle Kolyada
2018-12-08 15:22 Mikle Kolyada
2018-10-15 19:03 Fabian Groffen
2018-09-29  8:29 Kent Fredric
2018-07-23  0:54 Mikle Kolyada
2018-07-21 13:27 Kent Fredric
2018-06-28 14:56 Mikle Kolyada
2018-06-26 12:28 Tobias Klausmann
2018-06-23 13:38 Mart Raudsepp
2018-06-10 21:33 Sergei Trofimovich
2018-06-10 19:03 Aaron Bauman
2018-06-10 16:42 Thomas Deutschmann
2018-06-09 18:54 Sergei Trofimovich
2018-03-14  3:44 Kent Fredric
2018-01-28 19:43 Patrice Clement
2017-01-29 16:59 Fabian Groffen
2017-01-28 14:13 Fabian Groffen
2016-09-17  8:56 Pacho Ramos
2016-07-18 17:26 Markus Meier
2016-07-17 17:02 Tobias Klausmann
2016-04-26 20:03 Andreas Hüttel
2016-01-24 12:11 Andreas Hüttel
2016-01-17 19:06 Mikle Kolyada
2016-01-11  9:07 Agostino Sarubbo
2016-01-10 10:34 Agostino Sarubbo
2016-01-09 18:50 Markus Meier
2016-01-09  6:43 Agostino Sarubbo
2016-01-02 18:53 Agostino Sarubbo
2015-09-09 19:43 Andreas Hüttel

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=1453621133.902d2d177a32fdf19f4b8d51074c2940aacb4ffc.jer@gentoo \
    --to=jer@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