From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-emacs/key-chord/
Date: Fri, 28 Apr 2023 00:05:04 +0000 (UTC) [thread overview]
Message-ID: <1682640271.6bbbac969fae0f0f1b525285a496c623ca6c2c94.sam@gentoo> (raw)
commit: 6bbbac969fae0f0f1b525285a496c623ca6c2c94
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Apr 28 00:04:00 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Apr 28 00:04:31 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6bbbac96
app-emacs/key-chord: Keyword 0.6_p20201222 ppc, #905201
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-emacs/key-chord/key-chord-0.6_p20201222.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-emacs/key-chord/key-chord-0.6_p20201222.ebuild b/app-emacs/key-chord/key-chord-0.6_p20201222.ebuild
index 00c36ea98698..cef500201d37 100644
--- a/app-emacs/key-chord/key-chord-0.6_p20201222.ebuild
+++ b/app-emacs/key-chord/key-chord-0.6_p20201222.ebuild
@@ -15,7 +15,7 @@ S="${WORKDIR}"/${PN}-${COMMIT}
LICENSE="GPL-2+"
SLOT="0"
-KEYWORDS="amd64 x86"
+KEYWORDS="amd64 ~ppc x86"
DOCS=( README.md )
SITEFILE="50${PN}-gentoo.el"
next reply other threads:[~2023-04-28 0:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 0:05 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-03 20:35 [gentoo-commits] repo/gentoo:master commit in: app-emacs/key-chord/ Maciej Barć
2025-05-05 23:09 Sam James
2025-05-05 23:09 Sam James
2025-04-03 20:39 Maciej Barć
2024-11-23 20:33 Arthur Zamarin
2024-02-15 10:05 Jakov Smolić
2024-02-14 19:47 Arthur Zamarin
2024-01-12 23:22 Maciej Barć
2023-04-29 13:06 Arthur Zamarin
2023-04-29 12:49 Arthur Zamarin
2023-04-28 3:41 Yixun Lan
2023-04-28 0:20 Sam James
2023-04-28 0:05 Sam James
2023-04-28 0:05 Sam James
2022-12-22 13:10 Sam James
2022-12-22 13:10 Sam James
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=1682640271.6bbbac969fae0f0f1b525285a496c623ca6c2c94.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