From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/dbf/
Date: Tue, 4 Jul 2023 16:10:31 +0000 (UTC) [thread overview]
Message-ID: <1688487021.4cc81e43d899008594cb2e900bff561eb1d3bbd8.sam@gentoo> (raw)
commit: 4cc81e43d899008594cb2e900bff561eb1d3bbd8
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Jul 4 16:10:21 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Jul 4 16:10:21 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4cc81e43
dev-ruby/dbf: Stabilize 4.2.4 amd64, #909631
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-ruby/dbf/dbf-4.2.4.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-ruby/dbf/dbf-4.2.4.ebuild b/dev-ruby/dbf/dbf-4.2.4.ebuild
index 0c944f772f91..da6ab452529b 100644
--- a/dev-ruby/dbf/dbf-4.2.4.ebuild
+++ b/dev-ruby/dbf/dbf-4.2.4.ebuild
@@ -17,5 +17,5 @@ HOMEPAGE="https://github.com/infused/dbf"
LICENSE="MIT"
SLOT="0"
-KEYWORDS="~amd64 ~x86"
+KEYWORDS="amd64 ~x86"
IUSE=""
next reply other threads:[~2023-07-04 16:10 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 16:10 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-06 14:27 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/dbf/ Sam James
2024-10-06 14:27 Sam James
2024-07-12 9:06 Hans de Graaff
2024-06-01 10:34 Arthur Zamarin
2024-06-01 10:25 Arthur Zamarin
2024-06-01 6:17 Hans de Graaff
2024-06-01 6:17 Hans de Graaff
2024-01-26 8:46 Hans de Graaff
2023-12-31 19:35 Hans de Graaff
2023-12-31 19:35 Hans de Graaff
2023-12-28 8:21 Hans de Graaff
2023-07-04 16:10 Sam James
2023-06-03 9:46 Hans de Graaff
2023-03-28 16:07 Sam James
2023-03-28 16:07 Sam James
2022-08-16 5:51 Hans de Graaff
2022-07-19 6:07 Hans de Graaff
2022-05-06 10:04 Hans de Graaff
2021-09-13 17:45 Hans de Graaff
2021-09-13 7:00 Agostino Sarubbo
2021-09-12 7:33 Sam James
2021-08-27 6:46 Hans de Graaff
2021-08-14 7:01 Hans de Graaff
2021-07-07 17:38 Hans de Graaff
2020-08-31 4:23 Hans de Graaff
2019-04-29 5:32 Hans de Graaff
2019-04-28 20:34 Thomas Deutschmann
2019-04-13 14:10 Mikle Kolyada
2019-04-11 18:29 Hans de Graaff
2019-02-23 10:05 Hans de Graaff
2019-02-23 10:05 Hans de Graaff
2019-01-27 7:49 Hans de Graaff
2019-01-11 7:33 Hans de Graaff
2018-10-17 5:13 Hans de Graaff
2018-06-18 5:18 Hans de Graaff
2018-06-06 23:49 Thomas Deutschmann
2018-05-24 14:31 Agostino Sarubbo
2018-04-27 5:42 Hans de Graaff
2017-12-25 7:05 Hans de Graaff
2017-10-27 5:56 Hans de Graaff
2017-10-23 18:42 Thomas Deutschmann
2017-10-22 7:11 Hans de Graaff
2017-10-21 7:27 Hans de Graaff
2017-05-17 4:59 Hans de Graaff
2017-05-16 8:01 Agostino Sarubbo
2017-05-15 14:17 Agostino Sarubbo
2017-01-01 6:41 Hans de Graaff
2017-01-01 6:41 Hans de Graaff
2016-12-16 6:42 Hans de Graaff
2016-10-13 5:25 Hans de Graaff
2016-10-13 5:25 Hans de Graaff
2016-08-30 5:40 Hans de Graaff
2016-08-19 6:00 Hans de Graaff
2016-04-03 22:12 Manuel Rüger
2016-02-15 6:17 Hans de Graaff
2016-01-30 15:50 Hans de Graaff
2016-01-30 15:50 Hans de Graaff
2015-12-20 20:21 Hans de Graaff
2015-11-29 7:29 Hans de Graaff
2015-11-10 6:37 Hans de Graaff
2015-11-10 6:37 Hans de Graaff
2015-10-24 6:01 Hans de Graaff
2015-10-10 5:39 Hans de Graaff
2015-10-02 5:27 Hans de Graaff
2015-08-17 5:57 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=1688487021.4cc81e43d899008594cb2e900bff561eb1d3bbd8.sam@gentoo \
--to=sam@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