public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/connection_pool/
Date: Sat, 22 Apr 2023 16:43:15 +0000 (UTC)	[thread overview]
Message-ID: <1682181784.b61158a5e9c0ae00a01dcd7e5cf83a0a5a095994.arthurzam@gentoo> (raw)

commit:     b61158a5e9c0ae00a01dcd7e5cf83a0a5a095994
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Sat Apr 22 16:43:04 2023 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Sat Apr 22 16:43:04 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b61158a5

dev-ruby/connection_pool: Stabilize 2.3.0 x86, #904204

Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>

 dev-ruby/connection_pool/connection_pool-2.3.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-ruby/connection_pool/connection_pool-2.3.0.ebuild b/dev-ruby/connection_pool/connection_pool-2.3.0.ebuild
index 9937d3537269..8c8f663f5818 100644
--- a/dev-ruby/connection_pool/connection_pool-2.3.0.ebuild
+++ b/dev-ruby/connection_pool/connection_pool-2.3.0.ebuild
@@ -17,7 +17,7 @@ SRC_URI="https://github.com/mperham/connection_pool/archive/v${PV}.tar.gz -> ${P
 
 LICENSE="MIT"
 SLOT="0"
-KEYWORDS="amd64 arm arm64 ~hppa ~loong ppc ~ppc64 ~riscv ~s390 ~sparc ~x86"
+KEYWORDS="amd64 arm arm64 ~hppa ~loong ppc ~ppc64 ~riscv ~s390 ~sparc x86"
 IUSE=""
 
 ruby_add_bdepend "test? ( >=dev-ruby/minitest-5 )"


             reply	other threads:[~2023-04-22 16:43 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-22 16:43 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-30 10:18 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/connection_pool/ Hans de Graaff
2023-12-27 20:33 Hans de Graaff
2023-12-27 20:33 Hans de Graaff
2023-12-05 18:25 Ionen Wolkens
2023-08-04  9:22 Sam James
2023-06-13 12:08 Hans de Graaff
2023-06-13 12:08 Hans de Graaff
2023-06-01  5:26 Sam James
2023-06-01  5:01 Sam James
2023-06-01  5:01 Sam James
2023-06-01  5:01 Sam James
2023-06-01  5:01 Sam James
2023-04-23 21:40 Sam James
2023-04-12 18:31 Arthur Zamarin
2023-04-12  3:28 Sam James
2023-04-12  2:36 Sam James
2023-04-12  2:36 Sam James
2023-03-26  6:35 Hans de Graaff
2023-03-12  7:40 Hans de Graaff
2022-05-08 15:00 WANG Xuerui
2022-03-31  6:15 Hans de Graaff
2022-03-30 11:48 Agostino Sarubbo
2022-03-28  6:51 Agostino Sarubbo
2022-03-27  9:54 Hans de Graaff
2022-03-27  9:54 Hans de Graaff
2021-11-08  2:51 Yixun Lan
2021-04-18  5:34 Hans de Graaff
2021-04-13  5:23 Hans de Graaff
2021-01-14  6:41 Hans de Graaff
2020-06-03  6:08 Hans de Graaff
2020-04-19 23:55 Sergei Trofimovich
2020-01-29  7:16 Hans de Graaff
2019-04-29  5:32 Hans de Graaff
2019-04-28 20:34 Thomas Deutschmann
2019-04-13 14:10 Mikle Kolyada
2019-01-09  8:07 Hans de Graaff
2018-05-25  5:03 Hans de Graaff
2017-12-27  7:02 Hans de Graaff
2017-12-27  7:02 Hans de Graaff
2017-12-27  7:02 Hans de Graaff
2017-06-30 12:47 Alexis Ballier
2017-05-06  6:41 Hans de Graaff
2016-11-13  7:17 Hans de Graaff
2016-03-28 10:21 Hans de Graaff
2016-02-14  6:53 Hans de Graaff
2015-09-19 17:25 Tobias Klausmann

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=1682181784.b61158a5e9c0ae00a01dcd7e5cf83a0a5a095994.arthurzam@gentoo \
    --to=arthurzam@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