From: "Ionen Wolkens" <ionen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/thor/
Date: Tue, 5 Dec 2023 18:25:47 +0000 (UTC) [thread overview]
Message-ID: <1701799089.235fe326568edb4c4966fb6680aa55f9102ce94d.ionen@gentoo> (raw)
commit: 235fe326568edb4c4966fb6680aa55f9102ce94d
Author: Matoro Mahri <matoro_gentoo <AT> matoro <DOT> tk>
AuthorDate: Tue Dec 5 17:49:14 2023 +0000
Commit: Ionen Wolkens <ionen <AT> gentoo <DOT> org>
CommitDate: Tue Dec 5 17:58:09 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=235fe326
dev-ruby/thor: Keyword 1.3.0 alpha, #917059
Signed-off-by: Matoro Mahri <matoro_gentoo <AT> matoro.tk>
Signed-off-by: Ionen Wolkens <ionen <AT> gentoo.org>
dev-ruby/thor/thor-1.3.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-ruby/thor/thor-1.3.0.ebuild b/dev-ruby/thor/thor-1.3.0.ebuild
index 2143223cbaa5..a9a663d09930 100644
--- a/dev-ruby/thor/thor-1.3.0.ebuild
+++ b/dev-ruby/thor/thor-1.3.0.ebuild
@@ -20,7 +20,7 @@ SRC_URI="https://github.com/rails/${PN}/archive/v${PV}.tar.gz -> ${PN}-git-${PV}
LICENSE="MIT"
SLOT="$(ver_cut 1)"
-KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~loong ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86 ~amd64-linux"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~loong ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86 ~amd64-linux"
IUSE="doc"
# For initial target porting (new rubies), we can make these test deps
next reply other threads:[~2023-12-05 18:25 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 18:25 Ionen Wolkens [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-15 12:47 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/thor/ Arthur Zamarin
2024-10-12 8:23 Hans de Graaff
2024-10-09 2:53 Jakov Smolić
2024-10-06 18:39 Arthur Zamarin
2024-10-06 11:11 Sam James
2024-10-06 11:07 Arthur Zamarin
2024-10-06 11:00 Sam James
2024-08-30 5:28 Hans de Graaff
2024-07-02 3:56 Ionen Wolkens
2024-02-29 12:36 Hans de Graaff
2024-01-04 6:54 Hans de Graaff
2023-10-20 5:35 Hans de Graaff
2023-10-20 5:35 Hans de Graaff
2023-08-29 6:01 Hans de Graaff
2023-06-23 17:15 Hans de Graaff
2023-04-23 22:12 Sam James
2023-04-23 20:22 Sam James
2023-04-23 20:01 Sam James
2023-04-23 19:56 Sam James
2023-04-23 19:50 Sam James
2023-04-23 19:50 Sam James
2023-04-02 5:07 Sam James
2023-03-24 3:58 Sam James
2023-03-19 7:14 Hans de Graaff
2022-06-28 16:59 Arthur Zamarin
2022-06-28 16:47 Arthur Zamarin
2022-06-04 5:47 Hans de Graaff
2022-05-23 5:05 Hans de Graaff
2022-05-08 15:00 WANG Xuerui
2022-05-05 11:34 Jakov Smolić
2022-05-05 11:34 Jakov Smolić
2022-04-27 4:34 Arthur Zamarin
2022-04-26 13:45 Sam James
2022-04-01 5:15 Arthur Zamarin
2022-01-10 7:22 Hans de Graaff
2021-11-07 8:11 Hans de Graaff
2021-10-03 6:30 Hans de Graaff
2021-10-02 20:40 Sam James
2021-07-07 19:15 Hans de Graaff
2021-03-15 6:16 Hans de Graaff
2021-03-15 6:16 Hans de Graaff
2021-03-08 9:29 Hans de Graaff
2021-02-14 10:49 Hans de Graaff
2020-07-23 15:02 Hans de Graaff
2020-04-19 23:55 Sergei Trofimovich
2020-02-15 15:24 Hans de Graaff
2019-07-17 7:09 Hans de Graaff
2019-04-11 17:46 Hans de Graaff
2019-04-11 17:46 Hans de Graaff
2019-01-09 8:07 Hans de Graaff
2018-11-10 6:19 Hans de Graaff
2018-05-06 13:42 Mart Raudsepp
2018-05-01 17:17 Michał Górny
2018-04-27 8:33 Hans de Graaff
2018-04-27 8:33 Hans de Graaff
2018-04-19 4:36 Hans de Graaff
2018-03-25 12:41 Sergei Trofimovich
2018-03-25 12:41 Sergei Trofimovich
2018-03-22 20:23 Jeroen Roovers
2018-01-13 8:19 Hans de Graaff
2017-08-18 6:11 Hans de Graaff
2017-06-10 7:31 Hans de Graaff
2017-04-29 20:13 Jeroen Roovers
2016-09-28 8:17 Tobias Klausmann
2016-05-18 8:55 Fabian Groffen
2016-03-23 16:15 Richard Farina
2016-01-10 7:28 Hans de Graaff
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=1701799089.235fe326568edb4c4966fb6680aa55f9102ce94d.ionen@gentoo \
--to=ionen@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