From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-php/pecl-memcached/
Date: Sat, 23 Jan 2016 17:34:34 +0000 (UTC) [thread overview]
Message-ID: <1453570432.7bbb5ee88e8f11f48c5f0c50d249480aac839d6a.ago@gentoo> (raw)
commit: 7bbb5ee88e8f11f48c5f0c50d249480aac839d6a
Author: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Sat Jan 23 17:33:52 2016 +0000
Commit: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Sat Jan 23 17:33:52 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7bbb5ee8
dev-php/pecl-memcached: amd64 stable wrt bug #567712
Package-Manager: portage-2.2.26
RepoMan-Options: --include-arches="amd64"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>
dev-php/pecl-memcached/pecl-memcached-2.2.0-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-php/pecl-memcached/pecl-memcached-2.2.0-r1.ebuild b/dev-php/pecl-memcached/pecl-memcached-2.2.0-r1.ebuild
index cb650d7..5bb39e3 100644
--- a/dev-php/pecl-memcached/pecl-memcached-2.2.0-r1.ebuild
+++ b/dev-php/pecl-memcached/pecl-memcached-2.2.0-r1.ebuild
@@ -12,7 +12,7 @@ USE_PHP="php5-4 php5-5 php5-6"
inherit php-ext-pecl-r2
-KEYWORDS="~amd64 ~x86"
+KEYWORDS="amd64 ~x86"
DESCRIPTION="Interface PHP with memcached via libmemcached library"
LICENSE="PHP-3"
next reply other threads:[~2016-01-23 17:34 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-23 17:34 Agostino Sarubbo [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-11 13:00 [gentoo-commits] repo/gentoo:master commit in: dev-php/pecl-memcached/ Sam James
2024-11-11 13:00 Sam James
2024-11-11 13:00 Sam James
2024-11-10 2:26 Michael Orlitzky
2024-11-10 2:26 Michael Orlitzky
2023-10-23 21:41 Michael Orlitzky
2023-07-06 6:08 Sam James
2022-10-26 19:56 Conrad Kostecki
2022-08-01 12:11 Joonas Niilola
2022-08-01 12:11 Joonas Niilola
2022-08-01 8:02 Agostino Sarubbo
2022-08-01 8:02 Agostino Sarubbo
2022-05-16 23:31 Sam James
2022-05-03 17:30 Brian Evans
2022-03-18 18:06 Brian Evans
2021-11-23 15:18 Brian Evans
2021-08-27 15:31 Brian Evans
2021-01-11 15:05 Brian Evans
2020-11-03 12:58 Sam James
2020-10-28 16:18 Sam James
2020-10-28 16:18 Sam James
2020-10-26 16:12 Thomas Deutschmann
2020-02-11 18:15 Brian Evans
2020-01-28 17:31 Brian Evans
2020-01-28 17:31 Brian Evans
2019-12-12 15:21 Brian Evans
2019-12-09 23:33 Thomas Deutschmann
2019-11-28 21:02 Thomas Deutschmann
2019-11-26 1:04 Aaron Bauman
2019-11-17 21:54 Thomas Deutschmann
2019-11-17 21:01 Thomas Deutschmann
2019-11-03 13:59 Mikle Kolyada
2019-06-06 6:51 Agostino Sarubbo
2019-06-04 19:37 Brian Evans
2019-06-04 19:37 Brian Evans
2019-06-04 16:22 Brian Evans
2019-02-22 15:05 Brian Evans
2019-02-22 15:05 Brian Evans
2019-01-14 15:28 Thomas Deutschmann
2018-04-18 21:30 Aaron Bauman
2017-12-04 17:55 Brian Evans
2017-12-04 17:55 Brian Evans
2017-03-26 0:08 Michael Orlitzky
2017-03-04 15:06 Brian Evans
2017-03-04 13:46 Agostino Sarubbo
2017-03-04 13:38 Agostino Sarubbo
2017-02-04 15:57 Michael Orlitzky
2017-01-12 21:37 Brian Evans
2016-12-12 21:07 Michael Orlitzky
2016-12-12 16:23 Brian Evans
2016-07-14 21:03 Brian Evans
2016-02-14 10:11 Agostino Sarubbo
2015-12-25 16:20 Agostino Sarubbo
2015-12-07 14:08 Michael Orlitzky
2015-12-07 10:02 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=1453570432.7bbb5ee88e8f11f48c5f0c50d249480aac839d6a.ago@gentoo \
--to=ago@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