public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Brian Evans" <grknight@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: virtual/httpd-php/
Date: Fri, 12 Oct 2018 14:06:43 +0000 (UTC)	[thread overview]
Message-ID: <1539353194.ca2701056a7a25c2e295c3e170ccc4ebd4792e04.grknight@gentoo> (raw)

commit:     ca2701056a7a25c2e295c3e170ccc4ebd4792e04
Author:     Brian Evans <grknight <AT> gentoo <DOT> org>
AuthorDate: Fri Oct 12 14:05:14 2018 +0000
Commit:     Brian Evans <grknight <AT> gentoo <DOT> org>
CommitDate: Fri Oct 12 14:06:34 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ca270105

virtual/httpd-php: Mark alpha stable

Signed-off-by: Brian Evans <grknight <AT> gentoo.org>
Package-Manager: Portage-2.3.51, Repoman-2.3.11

 virtual/httpd-php/httpd-php-7.2.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/virtual/httpd-php/httpd-php-7.2.ebuild b/virtual/httpd-php/httpd-php-7.2.ebuild
index 1e585fbd471..591022a243b 100644
--- a/virtual/httpd-php/httpd-php-7.2.ebuild
+++ b/virtual/httpd-php/httpd-php-7.2.ebuild
@@ -5,7 +5,7 @@ EAPI="6"
 
 DESCRIPTION="Virtual to provide PHP-enabled webservers"
 SLOT="${PV}"
-KEYWORDS="~alpha amd64 arm ~arm64 ~hppa ia64 ~mips ppc ppc64 ~s390 ~sh sparc x86 ~amd64-fbsd ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos"
+KEYWORDS="alpha amd64 arm ~arm64 ~hppa ia64 ~mips ppc ppc64 ~s390 ~sh sparc x86 ~amd64-fbsd ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos"
 
 RDEPEND="|| ( dev-lang/php:${SLOT}[fpm]
 			  dev-lang/php:${SLOT}[apache2]


             reply	other threads:[~2018-10-12 14:06 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-12 14:06 Brian Evans [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-07  1:02 [gentoo-commits] repo/gentoo:master commit in: virtual/httpd-php/ Ionen Wolkens
2024-04-12  6:26 Arthur Zamarin
2024-03-07 20:24 Sam James
2024-03-07 18:41 Sam James
2024-03-07 18:19 Sam James
2024-02-19 19:57 Sam James
2024-02-10  8:04 Joonas Niilola
2023-10-11 19:16 Florian Schmaus
2023-02-20 19:51 Brian Evans
2023-02-16  5:52 WANG Xuerui
2022-10-28 19:37 Brian Evans
2022-10-19 10:50 WANG Xuerui
2022-09-30 17:14 Brian Evans
2022-06-22  7:05 Michał Górny
2022-04-05 19:03 Brian Evans
2021-10-05 17:59 Sam James
2021-10-03  0:37 Sam James
2021-10-02 23:54 Sam James
2021-09-30  7:12 Agostino Sarubbo
2021-09-29  7:57 Agostino Sarubbo
2021-09-29  7:57 Agostino Sarubbo
2021-09-29  7:56 Agostino Sarubbo
2021-09-26  0:27 Brian Evans
2021-08-29 18:43 Marek Szuba
2021-08-29 18:43 Marek Szuba
2021-02-25 19:23 Brian Evans
2020-12-15  2:17 Matt Turner
2020-12-08  1:07 Brian Evans
2020-03-17 20:48 Mart Raudsepp
2020-03-05 15:06 Agostino Sarubbo
2020-03-02 18:26 Sergei Trofimovich
2020-02-26 16:32 Sergei Trofimovich
2020-02-24 12:50 Agostino Sarubbo
2020-02-24 11:43 Agostino Sarubbo
2020-02-24 11:28 Agostino Sarubbo
2020-02-23 22:49 Thomas Deutschmann
2019-12-30 15:09 Brian Evans
2019-10-13 19:01 Matt Turner
2019-08-15 16:30 Brian Evans
2019-07-25 14:01 Brian Evans
2019-06-05 21:28 Thomas Deutschmann
2019-06-05 21:28 Thomas Deutschmann
2019-02-11 14:21 Brian Evans
2018-09-27 19:30 Brian Evans
2018-09-20 12:52 Brian Evans
2018-06-14 13:17 Brian Evans
2018-03-07 22:47 Sergei Trofimovich
2018-02-07  3:03 Brian Evans
2018-01-29  8:22 Tobias Klausmann
2018-01-15 19:49 Brian Evans
2017-12-16 17:24 Tobias Klausmann
2017-12-12 22:44 Sergei Trofimovich
2017-12-03 10:34 Sergei Trofimovich
2017-07-21 20:22 Brian Evans
2017-03-11 18:59 Agostino Sarubbo
2017-02-23 14:14 Brian Evans
2017-02-21 15:09 Brian Evans
2017-02-21  6:11 Jeroen Roovers
2017-02-20 13:54 Brian Evans
2016-12-05  2:48 Michael Orlitzky
2016-11-28 15:46 Brian Evans
2016-05-05 14:21 Brian Evans
2015-12-18 17:22 Brian Evans
2015-12-18 17:22 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=1539353194.ca2701056a7a25c2e295c3e170ccc4ebd4792e04.grknight@gentoo \
    --to=grknight@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