From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-emacs/bind-key/
Date: Fri, 28 Apr 2023 00:05:04 +0000 (UTC) [thread overview]
Message-ID: <1682640272.60d889139a291298fc7f249ed7af8fe6e18d39b8.sam@gentoo> (raw)
commit: 60d889139a291298fc7f249ed7af8fe6e18d39b8
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Apr 28 00:04:01 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Apr 28 00:04:32 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=60d88913
app-emacs/bind-key: Keyword 2.4.4 ppc, #905201
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-emacs/bind-key/bind-key-2.4.4.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/app-emacs/bind-key/bind-key-2.4.4.ebuild b/app-emacs/bind-key/bind-key-2.4.4.ebuild
index 5b5cc8256a7b..cf82f4231f33 100644
--- a/app-emacs/bind-key/bind-key-2.4.4.ebuild
+++ b/app-emacs/bind-key/bind-key-2.4.4.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2022 Gentoo Authors
+# Copyright 1999-2023 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=8
@@ -13,7 +13,7 @@ S="${WORKDIR}"/use-package-${PV}
LICENSE="GPL-3+"
SLOT="0"
-KEYWORDS="amd64 x86"
+KEYWORDS="amd64 ~ppc x86"
SITEFILE="50${PN}-gentoo.el"
next reply other threads:[~2023-04-28 0:05 UTC|newest]
Thread overview: 12+ 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 --
2023-04-29 13:06 [gentoo-commits] repo/gentoo:master commit in: app-emacs/bind-key/ Arthur Zamarin
2023-04-29 12:49 Arthur Zamarin
2023-04-28 16:52 Maciej Barć
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
2022-11-19 1:57 Maciej Barć
2022-04-26 2:15 Maciej Barć
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=1682640272.60d889139a291298fc7f249ed7af8fe6e18d39b8.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