public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-php/pecl-redis/
Date: Thu, 14 Mar 2019 19:18:54 +0000 (UTC)	[thread overview]
Message-ID: <1552591094.4306eea0f1ad64f8d531774b394a280c28486883.zlogene@gentoo> (raw)

commit:     4306eea0f1ad64f8d531774b394a280c28486883
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Thu Mar 14 19:18:14 2019 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Thu Mar 14 19:18:14 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4306eea0

dev-php/pecl-redis: amd64 stable wrt bug #678810

Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>
Package-Manager: Portage-2.3.62, Repoman-2.3.11
RepoMan-Options: --include-arches="amd64"

 dev-php/pecl-redis/pecl-redis-4.2.0.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/dev-php/pecl-redis/pecl-redis-4.2.0.ebuild b/dev-php/pecl-redis/pecl-redis-4.2.0.ebuild
index efc6fc7869d..f92d9dd8a0a 100644
--- a/dev-php/pecl-redis/pecl-redis-4.2.0.ebuild
+++ b/dev-php/pecl-redis/pecl-redis-4.2.0.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2018 Gentoo Authors
+# Copyright 1999-2019 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=6
@@ -15,7 +15,7 @@ inherit php-ext-pecl-r3
 DESCRIPTION="PHP extension for interfacing with Redis"
 LICENSE="PHP-3.01"
 SLOT="0"
-KEYWORDS="~amd64 ~arm"
+KEYWORDS="amd64 ~arm"
 IUSE="igbinary +session"
 
 DEPEND="


             reply	other threads:[~2019-03-14 19:19 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-14 19:18 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-14  6:35 [gentoo-commits] repo/gentoo:master commit in: dev-php/pecl-redis/ Sam James
2025-01-19  1:31 Sam James
2024-11-25  0:04 Sam James
2024-11-10  2:14 Michael Orlitzky
2024-01-12 21:50 Sam James
2023-12-28  1:28 Conrad Kostecki
2023-07-04 13:59 Sam James
2022-10-26 19:56 Conrad Kostecki
2022-10-26 19:56 Conrad Kostecki
2022-06-16  9:56 Jakov Smolić
2022-03-21 13:11 Brian Evans
2022-03-21  7:47 Agostino Sarubbo
2022-03-18 17:17 Brian Evans
2022-01-20 16:21 Brian Evans
2021-03-25 17:11 Brian Evans
2021-02-09 18:47 Thomas Deutschmann
2021-01-21 13:55 Brian Evans
2021-01-21  7:40 Agostino Sarubbo
2020-12-09 13:42 Brian Evans
2020-10-23  1:19 Thomas Deutschmann
2020-07-08 12:49 Thomas Deutschmann
2020-06-14 23:30 Thomas Deutschmann
2020-05-06 14:58 Brian Evans
2020-05-06  9:12 Agostino Sarubbo
2020-04-21 11:09 Thomas Deutschmann
2019-12-13  0:07 Thomas Deutschmann
2019-11-17 21:01 Thomas Deutschmann
2019-10-04 17:04 Brian Evans
2019-03-14 20:43 Brian Evans
2019-03-14 20:43 Brian Evans
2018-12-18  0:51 Thomas Deutschmann
2018-08-10 19:16 Brian Evans
2018-05-09 13:52 Brian Evans
2018-04-16 17:26 Michael Orlitzky
2018-04-16 17:10 Aaron Bauman
2018-04-16 16:47 Brian Evans
2018-04-06 14:24 Brian Evans
2018-03-14  6:00 Markus Meier
2018-01-09 16:34 Michael Orlitzky
2018-01-09 16:34 Michael Orlitzky
2017-12-08  1:41 Michael Orlitzky
2017-10-09 13:43 Brian Evans
2017-08-14 15:01 Brian Evans
2017-07-05  1:55 Brian Evans
2017-06-09 19:17 Brian Evans
2017-04-20 21:01 Brian Evans
2017-02-06 14:55 Brian Evans
2017-02-04  0:14 Michael Orlitzky
2017-01-17 14:38 Brian Evans
2017-01-05 20:39 Brian Evans
2017-01-03  5:50 Michael Orlitzky
2017-01-03  5:50 Michael Orlitzky
2016-12-06 14:40 Brian Evans
2016-08-19 14:23 Brian Evans
2016-06-14 20:01 Brian Evans
2016-01-23 19:40 Michael Orlitzky
2016-01-23 19:40 Michael Orlitzky
2016-01-23 17:34 Agostino Sarubbo
2015-12-08 21:45 Michael Orlitzky

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=1552591094.4306eea0f1ad64f8d531774b394a280c28486883.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