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/rspec-its/
Date: Fri,  1 Apr 2022 05:15:29 +0000 (UTC)	[thread overview]
Message-ID: <1648790069.39bf99bd7ac66ddc5e0a1664d16fcf3589605f28.arthurzam@gentoo> (raw)

commit:     39bf99bd7ac66ddc5e0a1664d16fcf3589605f28
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Fri Apr  1 05:14:29 2022 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Fri Apr  1 05:14:29 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=39bf99bd

dev-ruby/rspec-its: Stabilize 1.3.0-r1 ppc64, #836161

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

 dev-ruby/rspec-its/rspec-its-1.3.0-r1.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/dev-ruby/rspec-its/rspec-its-1.3.0-r1.ebuild b/dev-ruby/rspec-its/rspec-its-1.3.0-r1.ebuild
index 51771bbc0572..28c6b69b32ba 100644
--- a/dev-ruby/rspec-its/rspec-its-1.3.0-r1.ebuild
+++ b/dev-ruby/rspec-its/rspec-its-1.3.0-r1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2021 Gentoo Authors
+# Copyright 1999-2022 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=8
@@ -15,7 +15,7 @@ HOMEPAGE="https://github.com/rspec/rspec-its"
 
 LICENSE="MIT"
 SLOT="1"
-KEYWORDS="amd64 ~arm ~arm64 ~hppa ~ppc ~ppc64 ~riscv ~sparc x86"
+KEYWORDS="amd64 ~arm ~arm64 ~hppa ~ppc ppc64 ~riscv ~sparc x86"
 IUSE=""
 
 ruby_add_rdepend ">=dev-ruby/rspec-core-3.0.0 >=dev-ruby/rspec-expectations-3.0.0"


             reply	other threads:[~2022-04-01  5:15 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-01  5:15 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-06-02  5:24 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/rspec-its/ Hans de Graaff
2025-05-21  9:20 Sam James
2025-05-20 23:43 Sam James
2025-05-20 18:31 Arthur Zamarin
2025-05-20 17:44 Arthur Zamarin
2025-05-18 12:13 Arthur Zamarin
2025-05-18 10:34 Arthur Zamarin
2025-05-18 10:34 Arthur Zamarin
2025-05-18 10:18 Arthur Zamarin
2025-05-18 10:09 Sam James
2025-04-01 18:56 Hans de Graaff
2024-11-14  8:42 Hans de Graaff
2024-10-27  6:56 Hans de Graaff
2024-07-02  3:56 Ionen Wolkens
2023-12-31 10:29 Hans de Graaff
2023-12-05 18:25 Ionen Wolkens
2023-03-14  6:33 Hans de Graaff
2022-06-28 16:59 Arthur Zamarin
2022-06-28 16:47 Arthur Zamarin
2022-04-27  4:34 Arthur Zamarin
2021-09-21  5:08 Hans de Graaff
2021-09-19 21:39 Agostino Sarubbo
2021-09-19 21:35 Agostino Sarubbo
2021-09-12  7:03 Hans de Graaff
2021-08-11 14:29 Marek Szuba
2021-03-13  7:49 Hans de Graaff
2020-04-19 12:22 Sergei Trofimovich
2020-04-19 12:22 Sergei Trofimovich
2020-01-20  6:30 Hans de Graaff
2019-04-10  6:09 Hans de Graaff
2019-01-10 13:05 Hans de Graaff
2018-03-26  5:47 Hans de Graaff
2017-06-29 20:53 Sergei Trofimovich
2017-05-16  8:01 Agostino Sarubbo
2017-05-14  6:20 Hans de Graaff
2017-05-07  9:44 Hans de Graaff
2017-04-05 22:03 Michael Weber
2017-03-31 12:09 Agostino Sarubbo
2017-03-29  2:06 Jeroen Roovers
2016-04-07  5:18 Hans de Graaff
2016-03-28 22:06 Manuel Rüger
2016-03-28 22:06 Manuel Rüger

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=1648790069.39bf99bd7ac66ddc5e0a1664d16fcf3589605f28.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