From: "Jakov Smolić" <jsmolic@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/hatch-fancy-pypi-readme/
Date: Mon, 22 Aug 2022 14:30:00 +0000 (UTC) [thread overview]
Message-ID: <1661178568.736b5d12f12d5fabf15b0111ae81f4b3e98e33bc.jsmolic@gentoo> (raw)
commit: 736b5d12f12d5fabf15b0111ae81f4b3e98e33bc
Author: Yu Gu <guyu2876 <AT> gmail <DOT> com>
AuthorDate: Mon Aug 22 14:02:27 2022 +0000
Commit: Jakov Smolić <jsmolic <AT> gentoo <DOT> org>
CommitDate: Mon Aug 22 14:29:28 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=736b5d12
dev-python/hatch-fancy-pypi-readme: Keyword 22.3.0 riscv, #865739
Signed-off-by: Yu Gu <guyu2876 <AT> gmail.com>
Signed-off-by: Jakov Smolić <jsmolic <AT> gentoo.org>
.../hatch-fancy-pypi-readme/hatch-fancy-pypi-readme-22.3.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/hatch-fancy-pypi-readme/hatch-fancy-pypi-readme-22.3.0.ebuild b/dev-python/hatch-fancy-pypi-readme/hatch-fancy-pypi-readme-22.3.0.ebuild
index dcc5eeefb3d4..f6c65cec4810 100644
--- a/dev-python/hatch-fancy-pypi-readme/hatch-fancy-pypi-readme-22.3.0.ebuild
+++ b/dev-python/hatch-fancy-pypi-readme/hatch-fancy-pypi-readme-22.3.0.ebuild
@@ -19,7 +19,7 @@ SRC_URI="
LICENSE="MIT"
SLOT="0"
-KEYWORDS="~amd64 ~arm ~arm64 ~ia64 ~ppc ~ppc64 ~s390"
+KEYWORDS="~amd64 ~arm ~arm64 ~ia64 ~ppc ~ppc64 ~riscv ~s390"
RDEPEND="
dev-python/hatchling[${PYTHON_USEDEP}]
next reply other threads:[~2022-08-22 14:30 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 14:30 Jakov Smolić [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-08 18:31 [gentoo-commits] repo/gentoo:master commit in: dev-python/hatch-fancy-pypi-readme/ Michał Górny
2024-01-18 18:46 Michał Górny
2024-01-18 18:03 Arthur Zamarin
2024-01-01 14:41 Michał Górny
2023-12-31 7:17 Michał Górny
2023-07-08 10:47 Benda XU
2023-06-27 11:52 Michał Górny
2023-06-27 5:19 Jakov Smolić
2023-05-23 15:42 Michał Górny
2023-05-23 5:07 Michał Górny
2022-10-03 16:46 Arthur Zamarin
2022-10-03 8:31 Agostino Sarubbo
2022-10-03 8:30 Agostino Sarubbo
2022-10-03 8:29 Agostino Sarubbo
2022-10-03 8:28 Agostino Sarubbo
2022-10-03 8:26 Agostino Sarubbo
2022-10-03 8:24 Agostino Sarubbo
2022-10-03 0:44 Sam James
2022-10-02 19:17 Arthur Zamarin
2022-10-02 18:54 Arthur Zamarin
2022-10-02 1:01 Sam James
2022-09-26 4:14 Arthur Zamarin
2022-09-22 7:40 Michał Górny
2022-09-12 8:16 Michał Górny
2022-09-11 13:19 Michał Górny
2022-09-11 13:19 Michał Górny
2022-09-10 18:45 Arthur Zamarin
2022-08-31 18:25 Arthur Zamarin
2022-08-28 9:48 James Le Cuirot
2022-08-27 18:04 Arthur Zamarin
2022-08-22 17:39 WANG Xuerui
2022-08-22 17:33 WANG Xuerui
2022-08-19 7:00 Arthur Zamarin
2022-08-19 5:54 Arthur Zamarin
2022-08-19 5:27 Arthur Zamarin
2022-08-19 5:27 Arthur Zamarin
2022-08-19 5:24 Arthur Zamarin
2022-08-19 5:24 Arthur Zamarin
2022-08-18 18:11 Arthur Zamarin
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=1661178568.736b5d12f12d5fabf15b0111ae81f4b3e98e33bc.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