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/Term-Table/
Date: Sat,  4 Nov 2023 10:49:12 +0000 (UTC)	[thread overview]
Message-ID: <1699094869.4036dda4a69bad29f81d60d577c11ff54743816a.sam@gentoo> (raw)

commit:     4036dda4a69bad29f81d60d577c11ff54743816a
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Nov  4 10:47:49 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Nov  4 10:47:49 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4036dda4

dev-perl/Term-Table: Stabilize 0.17.0 arm64, #916825

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

 dev-perl/Term-Table/Term-Table-0.17.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-perl/Term-Table/Term-Table-0.17.0.ebuild b/dev-perl/Term-Table/Term-Table-0.17.0.ebuild
index c32317d88e97..03c56b78bfa2 100644
--- a/dev-perl/Term-Table/Term-Table-0.17.0.ebuild
+++ b/dev-perl/Term-Table/Term-Table-0.17.0.ebuild
@@ -10,7 +10,7 @@ inherit perl-module optfeature
 DESCRIPTION="Format a header and rows into a table"
 
 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"
 
 RDEPEND="
 	virtual/perl-Carp


             reply	other threads:[~2023-11-04 10:49 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-04 10:49 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-23  4:17 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Term-Table/ Sam James
2023-12-29 23:32 Sam James
2023-11-13  4:35 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-11-04 10:49 Sam James
2023-09-14 16:28 Sam James
2023-08-01 18:27 Arthur Zamarin
2023-07-24  7:45 Jakov Smolić
2023-07-24  7:45 Jakov Smolić
2023-06-18 21:53 Sam James
2021-12-09 12:05 Andreas K. Hüttel
2021-10-04 11:01 Agostino Sarubbo
2021-10-03  0:30 Sam James
2021-08-05 11:11 Sergei Trofimovich
2021-07-31 13:04 Agostino Sarubbo
2021-07-28  2:38 Sam James
2021-07-26  2:27 Sam James
2021-07-26  2:14 Sam James
2021-07-26  2:14 Sam James
2021-05-13 14:34 Andreas K. Hüttel
2020-04-15  7:08 Agostino Sarubbo
2020-04-14 15:45 Agostino Sarubbo
2020-04-14 14:06 Agostino Sarubbo
2020-04-12 11:39 Mart Raudsepp
2019-07-19  7:48 Mikle Kolyada
2019-02-23 20:14 Sergei Trofimovich
2019-01-09 10:52 Mikle Kolyada
2019-01-07  0:16 Thomas Deutschmann
2019-01-05 19:45 Sergei Trofimovich
2018-10-27 19:04 Fabian Groffen
2018-06-30 17:44 Mikle Kolyada
2018-02-22 14:43 Michał Górny
2017-12-27  8:35 Markus Meier
2017-12-22  5:20 Markus Meier
2017-11-25 18:51 Sergei Trofimovich
2017-11-23 22:31 Matt Turner
2017-11-13 22:28 Sergei Trofimovich
2017-11-09  0:07 Matt Turner
2017-10-16 20:51 Sergei Trofimovich
2017-10-14 14:46 Sergei Trofimovich

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=1699094869.4036dda4a69bad29f81d60d577c11ff54743816a.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