public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: www-apache/mod_perl/
Date: Mon,  7 Mar 2016 12:54:52 +0000 (UTC)	[thread overview]
Message-ID: <1457355272.80bdd5a6d50b25986b68d1f20bad96cbd99fff4e.ago@gentoo> (raw)

commit:     80bdd5a6d50b25986b68d1f20bad96cbd99fff4e
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Mon Mar  7 12:54:32 2016 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Mon Mar  7 12:54:32 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=80bdd5a6

www-apache/mod_perl: amd64 stable wrt bug #548932

Package-Manager: portage-2.2.26
RepoMan-Options: --include-arches="amd64"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>

 www-apache/mod_perl/mod_perl-2.0.10_pre201601.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/www-apache/mod_perl/mod_perl-2.0.10_pre201601.ebuild b/www-apache/mod_perl/mod_perl-2.0.10_pre201601.ebuild
index 2de8412..717c2db 100644
--- a/www-apache/mod_perl/mod_perl-2.0.10_pre201601.ebuild
+++ b/www-apache/mod_perl/mod_perl-2.0.10_pre201601.ebuild
@@ -13,7 +13,7 @@ SRC_URI="http://dev.gentoo.org/~dilfridge/distfiles/${P}.tar.gz"
 
 LICENSE="GPL-2"
 SLOT="1"
-KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86"
+KEYWORDS="~alpha amd64 ~arm ~hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86"
 IUSE="debug"
 
 # Make sure we always use the latest Apache-Test version or even check the


             reply	other threads:[~2016-03-07 12:55 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-07 12:54 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-27 17:55 [gentoo-commits] repo/gentoo:master commit in: www-apache/mod_perl/ Arthur Zamarin
2024-05-07  7:57 Andreas K. Hüttel
2024-01-18  8:06 Florian Schmaus
2024-01-18  8:06 Florian Schmaus
2024-01-18  8:06 Florian Schmaus
2024-01-18  8:06 Florian Schmaus
2023-11-13  4:35 Sam James
2023-09-02 14:32 Arthur Zamarin
2023-09-02 14:32 Arthur Zamarin
2023-09-02 14:32 Arthur Zamarin
2023-09-02 14:32 Arthur Zamarin
2023-07-05  1:25 Sam James
2022-08-26 10:46 Sam James
2020-06-13 21:09 Matt Turner
2020-05-11 16:49 Agostino Sarubbo
2020-05-06  6:28 Agostino Sarubbo
2020-05-05  6:46 Agostino Sarubbo
2020-05-04 16:56 Agostino Sarubbo
2020-03-17  9:44 Andreas K. Hüttel
2018-12-22 12:46 Andreas K. Hüttel
2018-07-23  8:15 Christian Ruppert
2017-04-30  9:37 Agostino Sarubbo
2017-04-19 21:32 Andreas Hüttel
2017-03-31  8:41 Michael Weber
2017-02-08  0:41 Robin H. Johnson
2017-02-02  0:06 Kent Fredric
2017-01-20 23:38 Andreas Hüttel
2017-01-14 13:52 Andreas Hüttel
2017-01-10  8:23 Aaron Bauman
2016-12-21 21:34 Thomas Deutschmann
2016-12-05 15:54 Tobias Klausmann
2016-11-25  8:44 Tobias Klausmann
2016-10-28 23:50 Andreas Hüttel
2016-10-21 23:28 Andreas Hüttel
2016-10-08 12:45 Patrice Clement
2016-10-01 18:11 Andreas Hüttel
2016-08-26  9:28 Pacho Ramos
2016-05-23 11:42 Tobias Klausmann
2016-01-22 17:38 Andreas Hüttel
2016-01-22  0:02 Andreas Hüttel
2016-01-09 19:31 Andreas Hüttel
2016-01-09 19:30 Andreas Hüttel
2015-11-22  8:02 Markus Meier

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=1457355272.80bdd5a6d50b25986b68d1f20bad96cbd99fff4e.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