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/unf_ext/
Date: Sat, 11 Mar 2023 05:27:38 +0000 (UTC)	[thread overview]
Message-ID: <1678512448.cc0958ead60901eb39a821d8d11fa336fe93a11a.arthurzam@gentoo> (raw)

commit:     cc0958ead60901eb39a821d8d11fa336fe93a11a
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Sat Mar 11 05:27:28 2023 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Sat Mar 11 05:27:28 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cc0958ea

dev-ruby/unf_ext: Stabilize 0.0.8.2 arm, #900739

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

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

diff --git a/dev-ruby/unf_ext/unf_ext-0.0.8.2.ebuild b/dev-ruby/unf_ext/unf_ext-0.0.8.2.ebuild
index fbd079be0f01..79135d4172d1 100644
--- a/dev-ruby/unf_ext/unf_ext-0.0.8.2.ebuild
+++ b/dev-ruby/unf_ext/unf_ext-0.0.8.2.ebuild
@@ -20,7 +20,7 @@ HOMEPAGE="https://github.com/knu/ruby-unf_ext"
 
 LICENSE="MIT"
 SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~loong ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~x86-solaris"
+KEYWORDS="~alpha ~amd64 arm ~arm64 ~hppa ~loong ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~x86-solaris"
 IUSE="doc test"
 
 ruby_add_bdepend "


             reply	other threads:[~2023-03-11  5:27 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-11  5:27 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-14  9:32 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/unf_ext/ Hans de Graaff
2024-05-26 23:02 Sam James
2024-05-26 23:02 Sam James
2024-05-26 23:02 Sam James
2024-05-26 23:02 Sam James
2024-05-26 22:43 Sam James
2024-05-26 22:43 Sam James
2024-05-26 22:43 Sam James
2023-12-27  7:55 Hans de Graaff
2023-11-17  7:46 Hans de Graaff
2023-11-12  7:07 Hans de Graaff
2023-11-12  7:07 Hans de Graaff
2023-03-11 17:24 Sam James
2023-03-11  8:07 Arthur Zamarin
2023-03-10 20:29 Hans de Graaff
2022-06-28 16:59 Arthur Zamarin
2022-06-28 16:47 Arthur Zamarin
2022-05-26  6:00 Hans de Graaff
2022-05-05 11:34 Jakov Smolić
2022-05-05 11:34 Jakov Smolić
2022-04-27  4:34 Arthur Zamarin
2022-04-01  5:15 Arthur Zamarin
2022-03-15  6:59 Hans de Graaff
2021-09-15  5:46 Hans de Graaff
2021-08-11 14:29 Marek Szuba
2021-07-31  6:47 Hans de Graaff
2021-07-30 15:17 Agostino Sarubbo
2021-07-30 15:14 Agostino Sarubbo
2021-07-19  6:27 Agostino Sarubbo
2021-07-19  6:26 Agostino Sarubbo
2021-07-19  6:25 Agostino Sarubbo
2021-07-03  6:26 Hans de Graaff
2021-04-04  6:53 Hans de Graaff
2021-01-06 18:32 Fabian Groffen
2020-03-30  6:07 Hans de Graaff
2020-01-02  6:50 Hans de Graaff
2019-07-05  4:21 Hans de Graaff
2019-07-04 18:23 Sergei Trofimovich
2019-05-13  1:41 Thomas Deutschmann
2019-04-30  9:50 Mikle Kolyada
2019-04-29  8:51 Sergei Trofimovich
2019-04-29  8:49 Sergei Trofimovich
2019-04-20  6:37 Hans de Graaff
2018-12-31  7:02 Hans de Graaff
2018-07-09 19:07 Sergei Trofimovich
2018-02-07  6:30 Hans de Graaff
2017-12-28 18:06 Sergei Trofimovich
2017-09-02  7:20 Hans de Graaff
2017-08-29 21:39 Thomas Deutschmann
2017-08-26 12:01 Mikle Kolyada
2017-08-25  7:03 Sergei Trofimovich
2017-08-23  6:14 Hans de Graaff
2017-04-19  4:23 Hans de Graaff
2017-04-13  5:30 Hans de Graaff
2017-02-07  5:26 Hans de Graaff
2016-09-28  8:17 Tobias Klausmann
2016-04-23  5:24 Hans de Graaff
2016-04-14 23:41 Manuel Rüger
2016-02-04  6:36 Hans de Graaff
2016-02-04  6:36 Hans de Graaff
2015-11-12 10:15 Agostino Sarubbo
2015-11-11  9:54 Agostino Sarubbo
2015-11-11  6:05 Jeroen Roovers
2015-11-09 11:24 Agostino Sarubbo

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=1678512448.cc0958ead60901eb39a821d8d11fa336fe93a11a.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