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/net-imap/
Date: Sat,  4 Mar 2023 10:25:09 +0000 (UTC)	[thread overview]
Message-ID: <1677925482.c700d94416884e02fde2574d27a93c41dd4c3bb2.graaff@gentoo> (raw)

commit:     c700d94416884e02fde2574d27a93c41dd4c3bb2
Author:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Tue Feb 28 07:43:51 2023 +0000
Commit:     Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Sat Mar  4 10:24:42 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c700d944

dev-ruby/net-imap: enable ruby32

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

 dev-ruby/net-imap/net-imap-0.3.4.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-ruby/net-imap/net-imap-0.3.4.ebuild b/dev-ruby/net-imap/net-imap-0.3.4.ebuild
index eaedc9142d36..61efc846ec37 100644
--- a/dev-ruby/net-imap/net-imap-0.3.4.ebuild
+++ b/dev-ruby/net-imap/net-imap-0.3.4.ebuild
@@ -2,7 +2,7 @@
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=8
-USE_RUBY="ruby27 ruby30 ruby31"
+USE_RUBY="ruby27 ruby30 ruby31 ruby32"
 
 RUBY_FAKEGEM_BINWRAP=""
 RUBY_FAKEGEM_EXTRADOC="README.md"


             reply	other threads:[~2023-03-04 10:25 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-04 10:25 Hans de Graaff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-02  8:21 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/net-imap/ Sam James
2025-02-16 17:49 Arthur Zamarin
2025-02-16 12:27 Sam James
2025-02-16 12:27 Sam James
2025-02-16 12:11 Sam James
2025-02-16 12:11 Sam James
2025-02-08  6:26 Hans de Graaff
2025-02-08  6:26 Hans de Graaff
2025-01-04 10:34 Hans de Graaff
2024-12-29  9:06 Hans de Graaff
2024-12-23  6:24 Hans de Graaff
2024-11-15  9:19 Arthur Zamarin
2024-11-14 18:41 Sam James
2024-11-14  4:35 Sam James
2024-11-14  4:00 Sam James
2024-11-14  3:23 Sam James
2024-11-14  3:17 Sam James
2024-11-14  2:49 Sam James
2024-11-11  7:39 Hans de Graaff
2024-11-04 19:35 Fabian Groffen
2024-10-14  5:56 Hans de Graaff
2024-10-12 15:05 Sam James
2024-10-11  8:47 Hans de Graaff
2024-10-10 16:20 Arthur Zamarin
2024-10-09  2:53 Jakov Smolić
2024-10-06 11:52 Sam James
2024-09-05  6:04 Hans de Graaff
2024-08-29  6:04 Hans de Graaff
2024-06-24  5:30 Hans de Graaff
2024-06-17  5:25 Hans de Graaff
2024-06-02  5:43 Hans de Graaff
2024-05-26  7:00 Sam James
2024-05-26  7:00 Sam James
2024-05-26  7:00 Sam James
2024-05-26  7:00 Sam James
2024-05-26  7:00 Sam James
2024-05-26  7:00 Sam James
2024-05-09  4:59 Hans de Graaff
2024-02-26 15:56 Hans de Graaff
2024-02-08  7:31 Hans de Graaff
2023-12-26 15:53 Hans de Graaff
2023-12-24  7:55 Hans de Graaff
2023-12-24  7:55 Hans de Graaff
2023-12-12  7:11 Hans de Graaff
2023-12-01  6:18 Hans de Graaff
2023-12-01  6:18 Hans de Graaff
2023-11-22  7:09 Hans de Graaff
2023-11-14  6:52 Hans de Graaff
2023-11-14  6:35 Hans de Graaff
2023-11-04  7:06 Hans de Graaff
2023-11-02  6:51 Hans de Graaff
2023-10-21  5:09 Hans de Graaff
2023-10-13 14:14 Arthur Zamarin
2023-10-12 23:32 Sam James
2023-10-12 12:05 Sam James
2023-10-12 10:33 Sam James
2023-10-12  5:48 Sam James
2023-10-12  5:48 Sam James
2023-10-12  5:48 Sam James
2023-10-12  5:48 Sam James
2023-10-12  5:19 Hans de Graaff
2023-08-02 16:55 Arthur Zamarin
2023-08-02 15:11 Sam James
2023-08-02  5:01 Sam James
2023-08-02  4:48 Sam James
2023-08-02  4:45 Sam James
2023-08-02  4:45 Sam James
2023-07-30  9:32 Hans de Graaff
2023-06-13  5:20 Hans de Graaff
2023-03-31  1:03 Sam James
2023-03-04 14:42 Hans de Graaff
2023-02-19  9:53 Hans de Graaff
2023-02-04  7:08 Hans de Graaff
2022-12-24 15:00 Hans de Graaff
2022-12-24 15:00 Hans de Graaff
2022-10-01  7:06 Hans de Graaff
2022-04-09 10:35 Hans de Graaff
2022-02-13  9:06 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=1677925482.c700d94416884e02fde2574d27a93c41dd4c3bb2.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