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/Class-Data-Inheritable/
Date: Mon, 15 Oct 2018 19:03:08 +0000 (UTC)	[thread overview]
Message-ID: <1539630177.016d270abb2aaece497bf493f4d4b344f3e418f0.grobian@gentoo> (raw)

commit:     016d270abb2aaece497bf493f4d4b344f3e418f0
Author:     Fabian Groffen <grobian <AT> gentoo <DOT> org>
AuthorDate: Mon Oct 15 18:45:44 2018 +0000
Commit:     Fabian Groffen <grobian <AT> gentoo <DOT> org>
CommitDate: Mon Oct 15 19:02:57 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=016d270a

dev-perl/Class-Data-Inheritable: added Prefix keywords, bug #665088

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

 .../Class-Data-Inheritable/Class-Data-Inheritable-0.80.0-r2.ebuild    | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/dev-perl/Class-Data-Inheritable/Class-Data-Inheritable-0.80.0-r2.ebuild b/dev-perl/Class-Data-Inheritable/Class-Data-Inheritable-0.80.0-r2.ebuild
index 188a06235d2..43ece3dea8a 100644
--- a/dev-perl/Class-Data-Inheritable/Class-Data-Inheritable-0.80.0-r2.ebuild
+++ b/dev-perl/Class-Data-Inheritable/Class-Data-Inheritable-0.80.0-r2.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
@@ -10,7 +10,7 @@ inherit perl-module
 DESCRIPTION="Inheritable, overridable class data"
 
 SLOT="0"
-KEYWORDS="alpha amd64 ~arm ~arm64 hppa ia64 ~mips ppc ppc64 ~s390 sparc x86 ~ppc-aix ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~sparc-solaris ~x86-solaris"
+KEYWORDS="alpha amd64 ~arm ~arm64 hppa ia64 ~mips ppc ppc64 ~s390 sparc x86 ~ppc-aix ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~m68k-mint ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
 IUSE=""
 
 export OPTIMIZE="${CFLAGS}"


             reply	other threads:[~2018-10-15 19:03 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-15 19:03 Fabian Groffen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-25 23:44 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Class-Data-Inheritable/ Sam James
2021-12-12 18:25 Sam James
2021-12-06  6:38 Arthur Zamarin
2021-12-05  3:15 Sam James
2021-12-05  3:11 Sam James
2021-12-05  3:09 Sam James
2021-10-10 17:44 Andreas K. Hüttel
2021-10-09 19:58 Andreas K. Hüttel
2020-10-04  5:05 Kent Fredric
2020-08-31 14:11 Sam James
2020-08-25 10:14 Sam James
2020-08-24 19:06 Sam James
2020-08-24  0:08 Sam James
2020-08-21 19:00 Sergei Trofimovich
2020-08-21 10:08 Sam James
2020-08-20 16:40 Sam James
2020-06-18 14:07 Kent Fredric
2018-08-04  0:54 Mikle Kolyada
2018-04-17  0:06 Kent Fredric
2018-04-08 15:48 Sergei Trofimovich
2018-04-07 21:13 Matt Turner
2018-04-07  4:01 Matt Turner
2018-04-05 21:07 Sergei Trofimovich
2018-04-05 18:29 Thomas Deutschmann
2018-04-05 16:10 Tobias Klausmann
2018-04-05 14:11 Aaron Bauman
2018-04-05  4:10 Kent Fredric
2017-12-22  5:20 Markus Meier
2017-10-18 21:39 Kent Fredric

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=1539630177.016d270abb2aaece497bf493f4d4b344f3e418f0.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