public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/Test-Warn/
Date: Sun,  5 Dec 2021 04:01:54 +0000 (UTC)	[thread overview]
Message-ID: <1638676851.37cb0cc29c87e4bfab72f40d137eca82fa975384.sam@gentoo> (raw)

commit:     37cb0cc29c87e4bfab72f40d137eca82fa975384
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Dec  5 04:00:51 2021 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Dec  5 04:00:51 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=37cb0cc2

dev-perl/Test-Warn: Stabilize 0.360.0 x86, #828211

Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-perl/Test-Warn/Test-Warn-0.360.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-perl/Test-Warn/Test-Warn-0.360.0.ebuild b/dev-perl/Test-Warn/Test-Warn-0.360.0.ebuild
index 96ef40d97e44..cf98314ce98c 100644
--- a/dev-perl/Test-Warn/Test-Warn-0.360.0.ebuild
+++ b/dev-perl/Test-Warn/Test-Warn-0.360.0.ebuild
@@ -10,7 +10,7 @@ inherit perl-module
 DESCRIPTION="Perl extension to test methods for warnings"
 
 SLOT="0"
-KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86 ~x64-cygwin ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
+KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc x86 ~x64-cygwin ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
 
 RDEPEND="
 	>=virtual/perl-Carp-1.220.0


             reply	other threads:[~2021-12-05  4:02 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-05  4:01 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-02 13:41 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Test-Warn/ Sam James
2023-08-02 13:25 Sam James
2023-06-18  3:40 Sam James
2021-12-10 20:56 Andreas K. Hüttel
2021-12-09 21:59 Sam James
2021-12-06  0:10 Sam James
2021-12-05  4:36 Sam James
2021-12-05  4:21 Sam James
2021-12-05  4:07 Sam James
2021-12-05  4:05 Sam James
2021-12-05  3:04 Sam James
2021-09-23 11:29 Andreas K. Hüttel
2020-07-24 18:58 Fabian Groffen
2019-07-25  6:48 Kent Fredric
2019-05-04 21:41 Mikle Kolyada
2019-01-03 18:57 Mikle Kolyada
2018-12-22 10:37 Mikle Kolyada
2018-12-08 15:22 Mikle Kolyada
2018-12-08 12:35 Mikle Kolyada
2018-12-01 15:10 Sergei Trofimovich
2018-11-23 13:06 Agostino Sarubbo
2018-10-27 19:04 Fabian Groffen
2018-10-12 11:16 Tobias Klausmann
2018-10-06 21:10 Mart Raudsepp
2018-10-06 19:34 Matt Turner
2018-10-02  7:33 Sergei Trofimovich
2018-10-01  0:07 Thomas Deutschmann
2018-09-30 16:08 Sergei Trofimovich
2018-03-09  6:45 Kent Fredric
2017-02-24  4:16 Mike Frysinger
2017-02-24  4:16 Mike Frysinger
2016-12-18  7:59 Kent Fredric
2016-08-11  9:03 Kent Fredric
2016-08-10 16:26 Kent Fredric
2016-08-04  3:29 Kent Fredric
2016-06-21 18:26 Markus Meier
2016-06-13 15:19 Tobias Klausmann
2016-06-10 15:32 Agostino Sarubbo
2016-03-01 14:46 Andreas Hüttel
2016-03-01 14:46 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=1638676851.37cb0cc29c87e4bfab72f40d137eca82fa975384.sam@gentoo \
    --to=sam@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