public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/thor/
Date: Thu, 10 Apr 2025 09:01:59 +0000 (UTC)	[thread overview]
Message-ID: <1744275548.fe656129f1542f0d4f3c17251c1a1cb1c7e181f0.graaff@gentoo> (raw)

commit:     fe656129f1542f0d4f3c17251c1a1cb1c7e181f0
Author:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Thu Apr 10 08:59:08 2025 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Thu Apr 10 08:59:08 2025 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fe656129

dev-ruby/thor: enable ruby34

Signed-off-by: Hans de Graaff <graaff <AT> gentoo.org>

 dev-ruby/thor/thor-1.3.2.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/dev-ruby/thor/thor-1.3.2.ebuild b/dev-ruby/thor/thor-1.3.2.ebuild
index 393e641ce092..b881c3dfd04f 100644
--- a/dev-ruby/thor/thor-1.3.2.ebuild
+++ b/dev-ruby/thor/thor-1.3.2.ebuild
@@ -1,9 +1,9 @@
-# Copyright 2000-2024 Gentoo Authors
+# Copyright 2000-2025 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=8
 
-USE_RUBY="ruby31 ruby32 ruby33"
+USE_RUBY="ruby31 ruby32 ruby33 ruby34"
 
 RUBY_FAKEGEM_RECIPE_TEST="rspec3"
 RUBY_FAKEGEM_DOCDIR="rdoc"


             reply	other threads:[~2025-04-10  9:02 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-10  9:01 Hans de Graaff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-07-19  6:07 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/thor/ Hans de Graaff
2025-04-10  9:01 Hans de Graaff
2024-10-15 12:47 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-12-05 18:25 Ionen Wolkens
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=1744275548.fe656129f1542f0d4f3c17251c1a1cb1c7e181f0.graaff@gentoo \
    --to=graaff@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