public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/regexp_property_values/
Date: Tue, 21 Apr 2020 21:06:39 +0000 (UTC)	[thread overview]
Message-ID: <1587503190.171c36c4bfd405eeec9440f459607da3f6948e40.slyfox@gentoo> (raw)

commit:     171c36c4bfd405eeec9440f459607da3f6948e40
Author:     Rolf Eike Beer <eike <AT> sf-mail <DOT> de>
AuthorDate: Tue Apr 21 20:12:03 2020 +0000
Commit:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Tue Apr 21 21:06:30 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=171c36c4

dev-ruby/regexp_property_values: keyworded 1.0.0 for sparc

Package-Manager: Portage-2.3.89, Repoman-2.3.20
RepoMan-Options: --include-arches="sparc"
Signed-off-by: Rolf Eike Beer <eike <AT> sf-mail.de>
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>

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

diff --git a/dev-ruby/regexp_property_values/regexp_property_values-1.0.0.ebuild b/dev-ruby/regexp_property_values/regexp_property_values-1.0.0.ebuild
index 96471aa238a..af384d45c02 100644
--- a/dev-ruby/regexp_property_values/regexp_property_values-1.0.0.ebuild
+++ b/dev-ruby/regexp_property_values/regexp_property_values-1.0.0.ebuild
@@ -21,7 +21,7 @@ SRC_URI="https://github.com/janosch-x/regexp_property_values/archive/v${PV}.tar.
 
 LICENSE="MIT"
 SLOT="1"
-KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~x86"
+KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~sparc ~x86"
 IUSE=""
 
 all_ruby_prepare() {


             reply	other threads:[~2020-04-21 21:06 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21 21:06 Sergei Trofimovich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-06 11:14 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/regexp_property_values/ Sam James
2024-05-23  6:13 Hans de Graaff
2024-01-08  7:19 Hans de Graaff
2023-12-31 10:29 Hans de Graaff
2023-12-31 10:29 Hans de Graaff
2023-07-24 10:05 Jakov Smolić
2023-06-12  6:21 Hans de Graaff
2023-06-12  6:21 Hans de Graaff
2023-03-14  6:33 Hans de Graaff
2022-04-08  9:15 Hans de Graaff
2022-04-08  9:15 Hans de Graaff
2022-04-02  8:57 Hans de Graaff
2022-04-02  8:57 Hans de Graaff
2022-01-09  7:17 Hans de Graaff
2021-12-07  6:42 Hans de Graaff
2021-12-07  6:42 Hans de Graaff
2021-12-07  6:42 Hans de Graaff
2021-10-24  8:05 Hans de Graaff
2021-09-07 21:28 Marek Szuba
2021-05-04  5:29 Hans de Graaff
2020-12-20 19:14 Sam James
2020-12-20 19:03 Sam James
2020-09-16  6:18 Hans de Graaff
2020-07-26 15:12 Hans de Graaff
2020-04-21 21:06 Sergei Trofimovich
2020-01-27  6:40 Hans de Graaff
2020-01-27  6:40 Hans de Graaff
2019-07-22 21:06 Hans de Graaff
2019-07-22 16:56 Aaron Bauman
2019-07-17  6:01 Hans de Graaff
2019-07-17  6:01 Hans de Graaff
2019-07-09 23:11 Sergei Trofimovich
2019-04-27  6:06 Hans de Graaff
2019-04-03  5:46 Hans de Graaff
2019-01-05  9:48 Hans de Graaff
2018-11-26 19:23 Mikle Kolyada
2018-11-17 23:18 Thomas Deutschmann
2018-11-11  6:40 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=1587503190.171c36c4bfd405eeec9440f459607da3f6948e40.slyfox@gentoo \
    --to=slyfox@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