From: "Jakov Smolić" <jsmolic@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/timecop/
Date: Tue, 15 Mar 2022 19:44:03 +0000 (UTC) [thread overview]
Message-ID: <1647373434.52ee02a093ed8d2e041020dcf81695ce484442d7.jsmolic@gentoo> (raw)
commit: 52ee02a093ed8d2e041020dcf81695ce484442d7
Author: Jakov Smolić <jsmolic <AT> gentoo <DOT> org>
AuthorDate: Tue Mar 15 19:43:54 2022 +0000
Commit: Jakov Smolić <jsmolic <AT> gentoo <DOT> org>
CommitDate: Tue Mar 15 19:43:54 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=52ee02a0
dev-ruby/timecop: Stabilize 0.9.4 x86, #835167
Signed-off-by: Jakov Smolić <jsmolic <AT> gentoo.org>
dev-ruby/timecop/timecop-0.9.4.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-ruby/timecop/timecop-0.9.4.ebuild b/dev-ruby/timecop/timecop-0.9.4.ebuild
index 10f0f669df80..196bf1370c3d 100644
--- a/dev-ruby/timecop/timecop-0.9.4.ebuild
+++ b/dev-ruby/timecop/timecop-0.9.4.ebuild
@@ -18,7 +18,7 @@ HOMEPAGE="https://github.com/travisjeffery/timecop"
LICENSE="MIT"
SLOT="0"
-KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ~ppc ~ppc64 ~riscv ~sparc ~x86"
+KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ~ppc ~ppc64 ~riscv ~sparc x86"
IUSE=""
# Missing testdep activesupport
next reply other threads:[~2022-03-15 21:27 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 19:44 Jakov Smolić [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-23 7:12 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/timecop/ Sam James
2024-09-18 8:56 Hans de Graaff
2024-06-20 5:30 Hans de Graaff
2024-06-20 5:30 Hans de Graaff
2024-06-02 5:43 Hans de Graaff
2024-01-06 8:02 Hans de Graaff
2023-08-22 5:07 Hans de Graaff
2023-08-13 8:40 Hans de Graaff
2023-08-13 5:22 Hans de Graaff
2023-08-13 5:22 Hans de Graaff
2023-04-23 22:16 Sam James
2023-04-23 20:05 Sam James
2023-04-23 20:01 Sam James
2023-04-23 19:55 Sam James
2023-04-23 19:53 Sam James
2023-04-23 19:50 Sam James
2023-04-23 19:50 Sam James
2023-03-28 19:24 Sam James
2023-03-28 19:24 Sam James
2023-03-28 19:24 Sam James
2023-03-28 19:24 Sam James
2023-03-28 19:15 Sam James
2023-03-28 19:15 Sam James
2023-03-28 19:05 Sam James
2023-03-23 6:53 Sam James
2023-03-23 6:53 Sam James
2023-03-18 23:10 Sam James
2022-04-26 13:45 Sam James
2022-03-31 5:39 Hans de Graaff
2022-03-19 12:00 Hans de Graaff
2022-03-19 6:53 Arthur Zamarin
2022-03-18 8:29 Arthur Zamarin
2022-03-17 7:45 Agostino Sarubbo
2022-03-17 7:42 Agostino Sarubbo
2022-03-15 9:38 Jakov Smolić
2022-03-15 6:59 Hans de Graaff
2022-03-15 6:59 Hans de Graaff
2021-08-11 14:29 Marek Szuba
2021-03-20 8:47 Hans de Graaff
2021-03-20 8:47 Hans de Graaff
2021-02-09 5:47 Hans de Graaff
2020-10-15 4:58 Hans de Graaff
2020-05-02 6:30 Hans de Graaff
2020-04-28 9:40 Agostino Sarubbo
2020-01-22 7:54 Hans de Graaff
2019-07-06 8:40 Hans de Graaff
2019-05-26 7:04 Sergei Trofimovich
2019-05-23 13:15 Mikle Kolyada
2019-05-20 17:50 Sergei Trofimovich
2019-05-12 20:56 Thomas Deutschmann
2019-05-11 7:15 Hans de Graaff
2019-04-29 8:51 Sergei Trofimovich
2019-04-29 8:49 Sergei Trofimovich
2019-04-28 20:59 Sergei Trofimovich
2019-01-09 8:07 Hans de Graaff
2018-07-09 19:07 Sergei Trofimovich
2018-07-04 20:56 Hans de Graaff
2018-03-29 6:46 Hans de Graaff
2017-12-20 21:53 Sergei Trofimovich
2017-12-20 21:53 Sergei Trofimovich
2017-12-02 6:30 Hans de Graaff
2017-08-09 6:21 Patrice Clement
2017-07-06 8:15 Agostino Sarubbo
2017-07-06 4:56 Hans de Graaff
2017-07-06 4:56 Hans de Graaff
2017-07-01 13:45 Alexis Ballier
2017-06-28 20:49 Sergei Trofimovich
2017-06-23 3:38 Hans de Graaff
2017-03-02 7:02 Hans de Graaff
2016-12-09 6:59 Hans de Graaff
2016-07-21 19:38 Hans de Graaff
2016-07-05 8:49 Tobias Klausmann
2016-05-12 5:19 Hans de Graaff
2016-04-03 6:56 Hans de Graaff
2016-04-03 6:56 Hans de Graaff
2016-03-21 16:44 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=1647373434.52ee02a093ed8d2e041020dcf81695ce484442d7.jsmolic@gentoo \
--to=jsmolic@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