From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/Perl-Tidy/
Date: Sat, 4 Nov 2023 10:50:44 +0000 (UTC) [thread overview]
Message-ID: <1699095010.01afe2670dc3a6b34690c3535b9779847d76673c.sam@gentoo> (raw)
commit: 01afe2670dc3a6b34690c3535b9779847d76673c
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 4 10:50:10 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Nov 4 10:50:10 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=01afe267
dev-perl/Perl-Tidy: Stabilize 20230912.0.0 arm, #916823
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-perl/Perl-Tidy/Perl-Tidy-20230912.0.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-perl/Perl-Tidy/Perl-Tidy-20230912.0.0.ebuild b/dev-perl/Perl-Tidy/Perl-Tidy-20230912.0.0.ebuild
index e74aa67c13f5..97ec532e7b33 100644
--- a/dev-perl/Perl-Tidy/Perl-Tidy-20230912.0.0.ebuild
+++ b/dev-perl/Perl-Tidy/Perl-Tidy-20230912.0.0.ebuild
@@ -14,7 +14,7 @@ HOMEPAGE="https://perltidy.sourceforge.net/ https://metacpan.org/release/Perl-Ti
LICENSE="GPL-2+"
SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~loong ~m68k ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x64-solaris"
+KEYWORDS="~alpha ~amd64 arm ~arm64 ~hppa ~ia64 ~loong ~m68k ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x64-solaris"
BDEPEND="virtual/perl-ExtUtils-MakeMaker"
next reply other threads:[~2023-11-04 10:50 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-04 10:50 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-14 3:50 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Perl-Tidy/ Sam James
2024-07-27 11:59 Sam James
2024-06-14 0:43 Sam James
2024-06-09 21:21 Sam James
2024-06-09 21:12 Sam James
2024-05-11 1:09 Sam James
2024-05-01 7:54 Sam James
2023-11-04 16:13 Arthur Zamarin
2023-11-04 13:35 Sam James
2023-11-04 10:50 Sam James
2023-11-04 10:49 Sam James
2023-09-16 9:27 Sam James
2023-09-09 7:52 Sam James
2023-08-21 3:50 Sam James
2023-08-19 7:23 Sam James
2023-08-19 7:00 Arthur Zamarin
2023-08-19 6:33 Sam James
2023-08-19 6:07 Sam James
2023-08-19 6:03 Sam James
2023-08-19 6:01 Sam James
2023-08-02 4:27 Sam James
2023-07-24 4:15 Sam James
2023-07-24 4:12 Sam James
2023-06-19 1:47 Sam James
2023-06-11 15:37 Sam James
2022-02-22 9:30 Arthur Zamarin
2022-02-19 12:17 Arthur Zamarin
2022-02-19 12:02 Arthur Zamarin
2022-02-19 9:41 Arthur Zamarin
2022-02-19 8:18 Arthur Zamarin
2022-02-19 7:23 Arthur Zamarin
2022-02-19 3:41 Sam James
2022-02-19 3:38 Sam James
2021-11-25 18:03 Andreas K. Hüttel
2021-11-25 18:03 Andreas K. Hüttel
2021-10-11 15:25 Sam James
2021-10-11 15:18 Sam James
2021-10-11 8:10 Agostino Sarubbo
2021-10-11 5:15 Sam James
2021-10-11 3:13 Sam James
2021-10-11 3:13 Sam James
2021-10-11 3:10 Sam James
2021-07-30 20:19 Andreas K. Hüttel
2021-07-30 20:19 Andreas K. Hüttel
2020-07-06 2:51 Matt Turner
2020-04-14 15:45 Agostino Sarubbo
2020-04-14 14:06 Agostino Sarubbo
2020-04-14 14:03 Agostino Sarubbo
2020-04-14 12:59 Agostino Sarubbo
2020-04-12 11:39 Mart Raudsepp
2020-04-12 9:34 Sergei Trofimovich
2019-10-13 2:39 Andreas K. Hüttel
2019-09-13 23:51 Matt Turner
2019-07-25 6:48 Kent Fredric
2018-10-16 18:47 Fabian Groffen
2018-09-01 19:01 Thomas Deutschmann
2018-08-20 4:40 Matt Turner
2018-08-04 0:54 Mikle Kolyada
2018-07-27 7:12 Sergei Trofimovich
2018-07-27 7:08 Sergei Trofimovich
2018-07-24 0:12 Mikle Kolyada
2018-07-23 6:19 Sergei Trofimovich
2018-03-28 17:27 Matt Turner
2017-12-26 8:48 Kent Fredric
2017-05-30 1:15 Kent Fredric
2017-04-17 23:16 Michael Weber
2017-02-22 21:45 Markus Meier
2016-12-04 16:43 Michael Palimaka
2016-05-24 22:38 Andreas Hüttel
2016-05-24 22:38 Andreas Hüttel
2016-03-19 22:42 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=1699095010.01afe2670dc3a6b34690c3535b9779847d76673c.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