public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Fabian Groffen" <grobian@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/Net-IDN-Encode/
Date: Sat, 27 Oct 2018 12:31:10 +0000 (UTC)	[thread overview]
Message-ID: <1540643463.ea6128a40a46558e15b28e56a942bb31fc69bd93.grobian@gentoo> (raw)

commit:     ea6128a40a46558e15b28e56a942bb31fc69bd93
Author:     Fabian Groffen <grobian <AT> gentoo <DOT> org>
AuthorDate: Sat Oct 27 12:23:13 2018 +0000
Commit:     Fabian Groffen <grobian <AT> gentoo <DOT> org>
CommitDate: Sat Oct 27 12:31:03 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ea6128a4

dev-perl/Net-IDN-Encode: added Prefix keywords, bug #665088

Signed-off-by: Fabian Groffen <grobian <AT> gentoo.org>
Package-Manager: Portage-2.3.49, Repoman-2.3.11

 dev-perl/Net-IDN-Encode/Net-IDN-Encode-2.400.0.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/dev-perl/Net-IDN-Encode/Net-IDN-Encode-2.400.0.ebuild b/dev-perl/Net-IDN-Encode/Net-IDN-Encode-2.400.0.ebuild
index cc04572c3fe..dc91e7596bc 100644
--- a/dev-perl/Net-IDN-Encode/Net-IDN-Encode-2.400.0.ebuild
+++ b/dev-perl/Net-IDN-Encode/Net-IDN-Encode-2.400.0.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2018 Gentoo Foundation
+# Copyright 1999-2018 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=6
@@ -11,7 +11,7 @@ inherit perl-module
 DESCRIPTION="Internationalizing Domain Names in Applications (IDNA)"
 
 SLOT="0"
-KEYWORDS="~alpha amd64 ~ia64 ppc ~ppc64 ~sparc x86"
+KEYWORDS="~alpha amd64 ~ia64 ppc ~ppc64 ~sparc x86 ~ppc-aix ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~m68k-mint ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
 IUSE="test"
 
 RDEPEND="


             reply	other threads:[~2018-10-27 12:31 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-27 12:31 Fabian Groffen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-02 14:58 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Net-IDN-Encode/ Arthur Zamarin
2023-09-06 15:05 Sam James
2023-09-06 15:03 Sam James
2023-09-06 15:03 Sam James
2023-09-06 15:03 Sam James
2023-09-06 15:03 Sam James
2023-09-06 15:03 Sam James
2023-04-03 19:10 Arthur Zamarin
2023-04-01 18:14 Arthur Zamarin
2023-03-17 20:44 Arthur Zamarin
2021-07-12 20:49 Andreas K. Hüttel
2021-07-12 20:49 Andreas K. Hüttel
2020-07-06  2:51 Matt Turner
2020-04-14 14:03 Agostino Sarubbo
2020-04-14 12:59 Agostino Sarubbo
2019-07-17  5:54 Kent Fredric
2019-03-14  7:36 Sergei Trofimovich
2019-01-17 20:39 Mikle Kolyada
2019-01-12  1:59 Kent Fredric
2018-10-29  4:06 Matt Turner
2018-10-18  7:52 Tobias Klausmann
2018-09-08  5:30 Mikle Kolyada
2018-09-07 23:03 Sergei Trofimovich
2018-09-07 22:37 Sergei Trofimovich
2018-09-02 11:48 Sergei Trofimovich
2018-07-22 14:51 Thomas Deutschmann
2018-07-15  3:40 Kent Fredric
2017-01-08  3:52 Kent Fredric
2016-12-19 14:14 Tobias Klausmann
2016-12-11 15:51 Kent Fredric
2016-12-08 19:09 Kent Fredric
2016-12-05 19:35 Kent Fredric
2016-03-31 21:44 Andreas Hüttel
2016-03-01 14:39 Andreas Hüttel
2016-01-24 12:37 Andreas Hüttel

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=1540643463.ea6128a40a46558e15b28e56a942bb31fc69bd93.grobian@gentoo \
    --to=grobian@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