From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-doc/halibut/
Date: Fri, 22 Jul 2022 17:55:19 +0000 (UTC) [thread overview]
Message-ID: <1658512508.0dab9c183de681ccc7a967f72ed66eded6d536a6.sam@gentoo> (raw)
commit: 0dab9c183de681ccc7a967f72ed66eded6d536a6
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Jul 22 17:55:08 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Jul 22 17:55:08 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0dab9c18
app-doc/halibut: Keyword 1.3 ppc64, #857231
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-doc/halibut/halibut-1.3.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-doc/halibut/halibut-1.3.ebuild b/app-doc/halibut/halibut-1.3.ebuild
index 92b0a35179b3..d4eb16bc2191 100644
--- a/app-doc/halibut/halibut-1.3.ebuild
+++ b/app-doc/halibut/halibut-1.3.ebuild
@@ -11,4 +11,4 @@ SRC_URI="https://www.chiark.greenend.org.uk/~sgtatham/${PN}/${P}/${P}.tar.gz"
LICENSE="MIT"
SLOT="0"
-KEYWORDS="amd64 ppc ~riscv x86"
+KEYWORDS="amd64 ppc ~ppc64 ~riscv x86"
next reply other threads:[~2022-07-22 17:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 17:55 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-09-19 6:42 [gentoo-commits] repo/gentoo:master commit in: app-doc/halibut/ Michał Górny
2022-09-17 5:38 Arthur Zamarin
2022-09-10 4:46 Sam James
2022-07-29 11:58 Arthur Zamarin
2022-07-29 10:26 Arthur Zamarin
2022-07-29 6:33 Arthur Zamarin
2022-05-31 7:12 Agostino Sarubbo
2022-05-31 7:11 Agostino Sarubbo
2022-05-31 7:09 Agostino Sarubbo
2022-05-30 17:15 Anthony G. Basile
2021-12-12 14:23 Yixun Lan
2020-09-26 14:33 Aaron Bauman
2017-12-16 10:31 Tobias Klausmann
2017-11-19 12:26 Sergei Trofimovich
2017-05-16 14:20 Anthony G. Basile
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=1658512508.0dab9c183de681ccc7a967f72ed66eded6d536a6.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