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/rb-inotify/
Date: Wed,  9 Oct 2024 07:16:17 +0000 (UTC)	[thread overview]
Message-ID: <1728458172.cb4085a4d0e184f156b7fb687d6a630d05576728.arthurzam@gentoo> (raw)

commit:     cb4085a4d0e184f156b7fb687d6a630d05576728
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Wed Oct  9 07:16:12 2024 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Wed Oct  9 07:16:12 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cb4085a4

dev-ruby/rb-inotify: Stabilize 0.11.1 arm64, #941038

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

 dev-ruby/rb-inotify/rb-inotify-0.11.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-ruby/rb-inotify/rb-inotify-0.11.1.ebuild b/dev-ruby/rb-inotify/rb-inotify-0.11.1.ebuild
index 8fe2e7fa854d..07359ab37267 100644
--- a/dev-ruby/rb-inotify/rb-inotify-0.11.1.ebuild
+++ b/dev-ruby/rb-inotify/rb-inotify-0.11.1.ebuild
@@ -17,7 +17,7 @@ SRC_URI="https://github.com/guard/rb-inotify/archive/refs/tags/v${PV}.tar.gz ->
 
 LICENSE="MIT"
 SLOT="0"
-KEYWORDS="~alpha amd64 arm ~arm64 ~hppa ~loong ppc ppc64 ~riscv ~s390 ~sparc x86 ~amd64-linux ~ppc-macos ~x64-macos ~x64-solaris"
+KEYWORDS="~alpha amd64 arm arm64 ~hppa ~loong ppc ppc64 ~riscv ~s390 ~sparc x86 ~amd64-linux ~ppc-macos ~x64-macos ~x64-solaris"
 IUSE=""
 
 ruby_add_rdepend "dev-ruby/ffi:0"


             reply	other threads:[~2024-10-09  7:16 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09  7:16 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-30  6:17 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/rb-inotify/ Hans de Graaff
2024-10-12 15:05 Sam James
2024-10-06 13:38 Arthur Zamarin
2024-10-06 11:36 Sam James
2024-10-06 11:35 Sam James
2024-10-06 11:12 Sam James
2024-05-19  5:33 Hans de Graaff
2024-05-19  5:33 Hans de Graaff
2024-01-06  8:02 Hans de Graaff
2023-12-05 18:25 Ionen Wolkens
2023-03-27 10:59 Sam James
2022-05-08 15:00 WANG Xuerui
2022-04-18 17:15 Hans de Graaff
2021-10-03  6:30 Hans de Graaff
2021-10-02 15:43 Sam James
2021-09-30 18:18 Sam James
2021-09-25  5:18 Agostino Sarubbo
2021-09-22  6:58 Agostino Sarubbo
2021-09-20  6:27 Agostino Sarubbo
2021-09-20  6:26 Agostino Sarubbo
2021-09-19 21:35 Agostino Sarubbo
2021-09-07 15:34 Marek Szuba
2021-03-27  6:09 Hans de Graaff
2020-11-06  3:21 Sam James
2020-01-24  7:23 Hans de Graaff
2019-12-25  6:56 Hans de Graaff
2019-06-05 17:56 Hans de Graaff
2019-06-04 13:30 Agostino Sarubbo
2019-05-23 13:15 Mikle Kolyada
2019-05-13  0:38 Thomas Deutschmann
2019-05-03 13:10 Mikle Kolyada
2019-04-28 20:59 Sergei Trofimovich
2019-04-28  9:48 Hans de Graaff
2019-04-10 17:27 Hans de Graaff
2019-01-09  8:07 Hans de Graaff
2018-12-16  6:35 Hans de Graaff
2018-07-10 19:11 Sergei Trofimovich
2018-04-28  6:33 Hans de Graaff
2018-01-23 19:27 Hans de Graaff
2018-01-23 19:07 Markus Meier
2018-01-21  8:56 Hans de Graaff
2017-12-30 11:02 Sergei Trofimovich
2017-12-12 18:39 Thomas Deutschmann
2017-12-11  6:36 Hans de Graaff
2017-12-10 22:39 Sergei Trofimovich
2017-12-04  7:04 Hans de Graaff
2017-07-01 13:45 Alexis Ballier
2017-06-19  5:23 Hans de Graaff
2017-06-17  5:22 Hans de Graaff
2017-05-07  9:44 Hans de Graaff
2017-05-07  9:44 Hans de Graaff
2017-04-29 20:13 Jeroen Roovers
2017-02-27 17:01 Michael Weber
2017-01-27  6:50 Hans de Graaff
2016-09-28  8:17 Tobias Klausmann
2016-07-18  6:49 Hans de Graaff
2016-07-12  4:38 Hans de Graaff
2016-07-12  4:38 Hans de Graaff
2016-07-12  4:38 Hans de Graaff
2016-05-18  8:49 Fabian Groffen
2016-04-25 23:21 Manuel Rüger
2016-02-09  6:04 Hans de Graaff
2016-02-06  6:52 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=1728458172.cb4085a4d0e184f156b7fb687d6a630d05576728.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