From: "Steve Arnold" <nerdboy@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/diskcache/
Date: Wed, 22 Jul 2020 21:43:54 +0000 (UTC) [thread overview]
Message-ID: <1595454201.4c1fd0122c117cae0b7adf1e1580b45cb39017b6.nerdboy@gentoo> (raw)
commit: 4c1fd0122c117cae0b7adf1e1580b45cb39017b6
Author: Stephen Arnold <nerdboy <AT> gentoo <DOT> org>
AuthorDate: Wed Jul 22 21:43:21 2020 +0000
Commit: Steve Arnold <nerdboy <AT> gentoo <DOT> org>
CommitDate: Wed Jul 22 21:43:21 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4c1fd012
dev-python/diskcache: keyword for arm/arm64
* extensively tested on arm and arm64 (mainly deque/cache)
* nothin new from repoman for either arm or arm64
Package-Manager: Portage-2.3.67, Repoman-2.3.17
Signed-off-by: Steve Arnold <nerdboy <AT> gentoo.org>
dev-python/diskcache/diskcache-4.1.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/diskcache/diskcache-4.1.0.ebuild b/dev-python/diskcache/diskcache-4.1.0.ebuild
index 36f1dadb121..9f91b9ac968 100644
--- a/dev-python/diskcache/diskcache-4.1.0.ebuild
+++ b/dev-python/diskcache/diskcache-4.1.0.ebuild
@@ -18,7 +18,7 @@ S=${WORKDIR}/python-diskcache-${PV}
LICENSE="Apache-2.0"
SLOT="0"
-KEYWORDS="~amd64 ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS="~amd64 ~arm ~arm64 ~x86 ~amd64-linux ~x86-linux"
BDEPEND="
test? (
next reply other threads:[~2020-07-22 21:43 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 21:43 Steve Arnold [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-19 17:32 [gentoo-commits] repo/gentoo:master commit in: dev-python/diskcache/ Michał Górny
2024-06-19 17:32 Michał Górny
2023-10-06 15:08 Michał Górny
2023-10-06 14:31 Sam James
2023-08-31 13:22 Michał Górny
2023-05-13 16:04 Michał Górny
2023-05-13 14:50 Jakov Smolić
2023-04-19 6:34 Michał Górny
2023-04-11 17:25 Michał Górny
2022-07-15 13:45 Arthur Zamarin
2022-04-01 7:45 Michał Górny
2022-04-01 5:15 Arthur Zamarin
2022-02-26 7:49 Michał Górny
2022-02-03 21:34 Michał Górny
2022-02-03 21:00 Arthur Zamarin
2022-02-02 7:29 Sam James
2022-01-01 1:29 Michał Górny
2021-12-31 18:44 Arthur Zamarin
2021-12-31 8:17 Michał Górny
2021-11-30 20:36 Michał Górny
2021-11-30 18:46 Michał Górny
2021-11-18 12:25 Agostino Sarubbo
2021-11-18 9:09 Sam James
2021-11-18 5:37 Sam James
2021-09-08 2:24 Yixun Lan
2021-07-25 3:16 Matt Turner
2021-07-24 17:30 Michał Górny
2021-07-24 15:12 Sam James
2021-07-07 0:33 Matt Turner
2021-06-20 21:08 Sergei Trofimovich
2021-06-20 1:45 Sam James
2021-06-19 15:29 Sergei Trofimovich
2021-06-15 15:40 Sergei Trofimovich
2021-06-14 10:36 Michał Górny
2021-06-14 10:06 Michał Górny
2021-06-14 6:34 Joshua Kinard
2021-06-12 2:53 Georgy Yakovlev
2021-02-25 19:36 Michał Górny
2021-02-25 18:58 Sam James
2021-01-23 8:55 Michał Górny
2021-01-18 19:45 Sam James
2021-01-18 18:03 Sam James
2021-01-18 12:09 Michał Górny
2021-01-18 12:01 Michał Górny
2020-11-09 8:14 Michał Górny
2020-09-18 14:41 Michał Górny
2020-09-09 7:18 Michał Górny
2020-08-30 5:16 Sam James
2020-08-27 7:00 Michał Górny
2020-08-24 6:35 Michał Górny
2020-05-04 10:48 Michał Górny
2020-04-21 8:08 Michał Górny
2020-01-25 20:54 Michał Górny
2020-01-25 20:54 Michał Górny
2018-11-18 22:00 Virgil Dupras
2017-08-14 22:32 Sebastien Fabbro
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=1595454201.4c1fd0122c117cae0b7adf1e1580b45cb39017b6.nerdboy@gentoo \
--to=nerdboy@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