From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-php/pecl-mailparse/
Date: Thu, 4 Oct 2018 09:12:46 +0000 (UTC) [thread overview]
Message-ID: <1538644361.1cc8779ea5703ea59c1e97f36bb2d5fd94aa697a.zlogene@gentoo> (raw)
commit: 1cc8779ea5703ea59c1e97f36bb2d5fd94aa697a
Author: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Thu Oct 4 09:12:29 2018 +0000
Commit: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Thu Oct 4 09:12:41 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1cc8779e
dev-php/pecl-mailparse: amd64 stable wrt bug #667084
Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>
Package-Manager: Portage-2.3.49, Repoman-2.3.11
dev-php/pecl-mailparse/pecl-mailparse-3.0.2-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-php/pecl-mailparse/pecl-mailparse-3.0.2-r1.ebuild b/dev-php/pecl-mailparse/pecl-mailparse-3.0.2-r1.ebuild
index ee23d5d211b..d9d400423ad 100644
--- a/dev-php/pecl-mailparse/pecl-mailparse-3.0.2-r1.ebuild
+++ b/dev-php/pecl-mailparse/pecl-mailparse-3.0.2-r1.ebuild
@@ -16,7 +16,7 @@ inherit php-ext-pecl-r3
# Only build for 7.x
USE_PHP="php7-0 php7-1 php7-2"
-KEYWORDS="~amd64 ~ppc ~ppc64 x86"
+KEYWORDS="amd64 ~ppc ~ppc64 x86"
DESCRIPTION="PHP extension for parsing and working with RFC822 and MIME compliant messages"
LICENSE="PHP-3.01"
next reply other threads:[~2018-10-04 9:12 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 9:12 Mikle Kolyada [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-10 2:02 [gentoo-commits] repo/gentoo:master commit in: dev-php/pecl-mailparse/ Michael Orlitzky
2024-09-20 11:01 Arthur Zamarin
2024-09-20 7:32 Arthur Zamarin
2024-09-20 7:19 Arthur Zamarin
2024-08-05 0:22 Michael Orlitzky
2022-07-13 17:43 Brian Evans
2022-07-01 8:16 Agostino Sarubbo
2022-07-01 6:30 Arthur Zamarin
2022-07-01 5:54 Arthur Zamarin
2022-06-30 19:36 Sam James
2022-06-30 15:10 Brian Evans
2022-06-30 14:27 Brian Evans
2022-05-03 16:58 Brian Evans
2022-05-03 16:58 Brian Evans
2021-10-15 14:33 Thomas Deutschmann
2021-01-27 19:21 Brian Evans
2021-01-25 22:58 Sam James
2021-01-24 13:33 Sam James
2021-01-24 12:10 Agostino Sarubbo
2021-01-22 16:53 Agostino Sarubbo
2020-12-08 21:40 Brian Evans
2020-09-30 18:05 Thomas Deutschmann
2020-07-08 12:49 Thomas Deutschmann
2020-05-15 12:57 Brian Evans
2020-05-06 14:30 Agostino Sarubbo
2020-05-06 9:12 Agostino Sarubbo
2020-05-06 7:18 Sergei Trofimovich
2020-05-06 7:01 Sergei Trofimovich
2019-12-22 22:20 Thomas Deutschmann
2019-10-14 13:09 Brian Evans
2019-10-14 13:09 Brian Evans
2019-04-05 20:21 Thomas Deutschmann
2018-10-14 9:14 Sergei Trofimovich
2018-10-14 8:59 Sergei Trofimovich
2018-10-01 21:47 Thomas Deutschmann
2018-10-01 19:14 Brian Evans
2018-04-06 18:30 Brian Evans
2017-07-05 1:44 Brian Evans
2017-03-07 17:30 Michael Weber
2017-03-02 10:47 Agostino Sarubbo
2017-02-27 8:24 Agostino Sarubbo
2016-12-20 9:44 Agostino Sarubbo
2016-12-19 19:14 Brian Evans
2016-12-19 18:45 Brian Evans
2016-08-23 20:58 Brian Evans
2016-08-22 20:41 Brian Evans
2016-07-19 13:00 Brian Evans
2016-07-19 13:00 Brian Evans
2016-07-13 17:02 Michael Orlitzky
2016-02-12 20:48 Brian Evans
2016-01-14 21:35 Brian Evans
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=1538644361.1cc8779ea5703ea59c1e97f36bb2d5fd94aa697a.zlogene@gentoo \
--to=zlogene@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