From: "Yixun Lan" <dlan@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libjodycode/
Date: Fri, 28 Jun 2024 14:29:49 +0000 (UTC) [thread overview]
Message-ID: <1719584962.af54249458a5a893f0e26041fd1c9dd25c6e7198.dlan@gentoo> (raw)
commit: af54249458a5a893f0e26041fd1c9dd25c6e7198
Author: Yixun Lan <dlan <AT> gentoo <DOT> org>
AuthorDate: Fri Jun 28 14:29:22 2024 +0000
Commit: Yixun Lan <dlan <AT> gentoo <DOT> org>
CommitDate: Fri Jun 28 14:29:22 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=af542494
dev-libs/libjodycode: Keyword 3.1 riscv, #934748
Signed-off-by: Yixun Lan <dlan <AT> gentoo.org>
dev-libs/libjodycode/libjodycode-3.1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-libs/libjodycode/libjodycode-3.1.ebuild b/dev-libs/libjodycode/libjodycode-3.1.ebuild
index c1166f08493a..81c3ce112d88 100644
--- a/dev-libs/libjodycode/libjodycode-3.1.ebuild
+++ b/dev-libs/libjodycode/libjodycode-3.1.ebuild
@@ -9,7 +9,7 @@ SRC_URI="https://github.com/jbruchon/libjodycode/archive/refs/tags/v${PV}.tar.gz
LICENSE="MIT"
SLOT="0"
-KEYWORDS="amd64 ~arm64"
+KEYWORDS="amd64 ~arm64 ~riscv"
# missing test script
# https://github.com/jbruchon/jdupes/issues/191
next reply other threads:[~2024-06-28 14:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 14:29 Yixun Lan [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-07 14:27 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libjodycode/ Sam James
2024-07-30 23:44 Jakov Smolić
2024-06-28 12:59 Sam James
2023-08-27 18:09 Jakov Smolić
2023-08-27 17:18 Sam James
2023-07-25 4:55 Joonas Niilola
2023-07-10 12:19 Jakov Smolić
2023-06-10 16:38 Jakov Smolić
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=1719584962.af54249458a5a893f0e26041fd1c9dd25c6e7198.dlan@gentoo \
--to=dlan@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