From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/Path-Tiny/
Date: Thu, 1 Mar 2018 14:28:19 +0000 (UTC) [thread overview]
Message-ID: <1519914488.6bc6aced51c68d237e5713e38dfb4860ade735f6.mgorny@gentoo> (raw)
commit: 6bc6aced51c68d237e5713e38dfb4860ade735f6
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Thu Mar 1 14:04:10 2018 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Thu Mar 1 14:28:08 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6bc6aced
dev-perl/Path-Tiny: Tested on ~amd64-fbsd
dev-perl/Path-Tiny/Path-Tiny-0.104.0.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/dev-perl/Path-Tiny/Path-Tiny-0.104.0.ebuild b/dev-perl/Path-Tiny/Path-Tiny-0.104.0.ebuild
index 272066f1d0c..c16d765a247 100644
--- a/dev-perl/Path-Tiny/Path-Tiny-0.104.0.ebuild
+++ b/dev-perl/Path-Tiny/Path-Tiny-0.104.0.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2017 Gentoo Foundation
+# Copyright 1999-2018 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
EAPI=6
@@ -11,7 +11,7 @@ DESCRIPTION="File path utility"
LICENSE="Apache-2.0"
SLOT="0"
-KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ppc ~ppc64 ~sparc x86"
+KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ppc ~ppc64 ~sparc x86 ~amd64-fbsd"
IUSE="test minimal"
RDEPEND="
next reply other threads:[~2018-03-01 14:28 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 14:28 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-14 0:43 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Path-Tiny/ Sam James
2024-06-09 21:24 Sam James
2024-06-09 21:12 Sam James
2024-06-09 21:08 Sam James
2024-06-09 20:36 Sam James
2024-05-08 20:34 Sam James
2023-07-24 4:16 Sam James
2023-07-24 4:00 Sam James
2023-07-24 4:00 Sam James
2023-06-19 17:59 Sam James
2022-05-14 6:54 WANG Xuerui
2022-02-22 9:30 Arthur Zamarin
2022-02-19 12:13 Arthur Zamarin
2022-02-19 12:02 Arthur Zamarin
2022-02-19 9:36 Arthur Zamarin
2022-02-19 8:18 Arthur Zamarin
2022-02-19 7:20 Arthur Zamarin
2022-02-19 3:41 Sam James
2022-02-19 3:38 Sam James
2021-11-24 16:18 Andreas K. Hüttel
2021-11-24 16:18 Andreas K. Hüttel
2021-08-26 19:51 Sam James
2021-08-26 14:55 Sam James
2021-08-26 14:52 Sam James
2021-08-25 16:26 Sam James
2021-08-25 5:32 Agostino Sarubbo
2021-08-25 5:25 Agostino Sarubbo
2021-07-25 11:16 Andreas K. Hüttel
2019-01-05 17:19 Mikle Kolyada
2018-10-27 12:45 Fabian Groffen
2018-10-11 14:56 Andreas Hüttel
2018-10-06 19:34 Matt Turner
2018-10-02 7:33 Sergei Trofimovich
2018-09-30 18:52 Sergei Trofimovich
2018-08-20 4:40 Matt Turner
2018-08-04 0:29 Mikle Kolyada
2018-04-15 21:10 Sergei Trofimovich
2018-03-28 4:09 Matt Turner
2017-07-07 7:33 Alexis Ballier
2017-05-31 2:49 Kent Fredric
2017-05-22 0:54 Michael Weber
2017-05-20 9:34 Agostino Sarubbo
2017-05-20 8:49 Agostino Sarubbo
2017-04-05 19:54 Kent Fredric
2017-03-10 21:04 Matt Turner
2016-07-24 9:49 Jeroen Roovers
2016-05-25 23:08 Matt Turner
2016-04-22 20:01 Markus Meier
2016-04-13 23:15 Andreas Hüttel
2016-03-16 22:50 Andreas Hüttel
2016-03-15 12:13 Agostino Sarubbo
2016-03-15 12:11 Agostino Sarubbo
2016-03-15 12:10 Agostino Sarubbo
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=1519914488.6bc6aced51c68d237e5713e38dfb4860ade735f6.mgorny@gentoo \
--to=mgorny@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