From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-portage/cpuid2cpuflags/
Date: Tue, 24 Dec 2019 14:21:27 +0000 (UTC) [thread overview]
Message-ID: <1577197032.975eccf2d3754995166f21f7d2cd2f70b883d471.zlogene@gentoo> (raw)
commit: 975eccf2d3754995166f21f7d2cd2f70b883d471
Author: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Tue Dec 24 14:17:12 2019 +0000
Commit: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Tue Dec 24 14:17:12 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=975eccf2
app-portage/cpuid2cpuflags: arm stable wrt bug #702708
Package-Manager: Portage-2.3.79, Repoman-2.3.16
RepoMan-Options: --include-arches="arm"
Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>
app-portage/cpuid2cpuflags/cpuid2cpuflags-8.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-portage/cpuid2cpuflags/cpuid2cpuflags-8.ebuild b/app-portage/cpuid2cpuflags/cpuid2cpuflags-8.ebuild
index c0e57ed3ad2..269ffe7851c 100644
--- a/app-portage/cpuid2cpuflags/cpuid2cpuflags-8.ebuild
+++ b/app-portage/cpuid2cpuflags/cpuid2cpuflags-8.ebuild
@@ -9,7 +9,7 @@ SRC_URI="https://github.com/mgorny/cpuid2cpuflags/releases/download/v${PV}/${P}.
LICENSE="BSD-2"
SLOT="0"
-KEYWORDS="amd64 ~arm ~arm64 ~ppc ~ppc64 x86 ~x64-macos ~x86-macos ~x64-solaris ~x86-solaris"
+KEYWORDS="amd64 arm ~arm64 ~ppc ~ppc64 x86 ~x64-macos ~x86-macos ~x64-solaris ~x86-solaris"
IUSE=""
pkg_postinst() {
next reply other threads:[~2019-12-24 14:21 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-24 14:21 Mikle Kolyada [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-23 3:40 [gentoo-commits] repo/gentoo:master commit in: app-portage/cpuid2cpuflags/ Michał Górny
2024-02-22 20:33 Arthur Zamarin
2024-02-08 17:10 Arthur Zamarin
2024-02-08 15:28 Michał Górny
2024-02-08 14:48 Michał Górny
2024-02-08 14:43 Michał Górny
2024-02-08 14:43 Michał Górny
2024-01-22 14:08 Michał Górny
2024-01-02 16:54 Michał Górny
2022-08-10 14:20 Michał Górny
2022-07-26 7:24 Michał Górny
2022-07-26 7:05 Sam James
2022-07-26 2:05 Sam James
2022-07-26 2:05 Sam James
2022-07-26 2:05 Sam James
2022-07-26 1:36 Sam James
2022-05-20 4:42 Michał Górny
2022-05-20 4:42 Michał Górny
2021-01-06 13:23 Fabian Groffen
2020-09-18 8:26 Agostino Sarubbo
2020-09-18 7:54 Agostino Sarubbo
2020-09-18 7:29 Agostino Sarubbo
2020-09-14 2:48 Sam James
2020-09-13 19:03 Sam James
2020-08-02 14:00 Michał Górny
2020-07-13 17:18 Michał Górny
2020-06-08 18:08 Georgy Yakovlev
2020-06-08 18:08 Georgy Yakovlev
2020-06-08 18:08 Georgy Yakovlev
2020-06-08 18:08 Georgy Yakovlev
2020-06-08 18:08 Georgy Yakovlev
2020-06-08 18:08 Georgy Yakovlev
2020-06-08 10:48 Michał Górny
2020-05-04 9:37 Michał Górny
2020-04-23 6:29 Agostino Sarubbo
2020-04-23 6:24 Agostino Sarubbo
2020-04-23 6:21 Agostino Sarubbo
2020-04-22 13:57 Mikle Kolyada
2020-04-21 10:13 Mart Raudsepp
2020-04-20 16:40 Georgy Yakovlev
2020-04-20 12:32 Michał Górny
2020-03-16 2:31 Georgy Yakovlev
2019-12-26 11:27 Michał Górny
2019-12-15 14:46 Agostino Sarubbo
2019-12-15 13:43 Agostino Sarubbo
2019-12-13 16:57 Michał Górny
2019-09-17 21:00 Michał Górny
2019-09-13 17:58 Mikle Kolyada
2019-09-11 10:19 Georgy Yakovlev
2019-09-10 20:03 Michał Górny
2019-09-09 5:54 Agostino Sarubbo
2019-09-08 19:15 Thomas Deutschmann
2019-07-19 18:15 Michał Górny
2019-01-12 15:38 Michał Górny
2018-03-15 16:17 Mikle Kolyada
2018-02-06 15:10 Thomas Deutschmann
2017-12-02 9:36 Michał Górny
2017-12-02 9:36 Michał Górny
2017-04-18 9:25 Alexis Ballier
2017-04-01 6:15 Michał Górny
2017-04-01 6:15 Michał Górny
2017-03-31 21:45 Michał Górny
2017-03-25 14:43 Agostino Sarubbo
2017-03-23 19:23 Michał Górny
2017-03-04 18:53 Michał Górny
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=1577197032.975eccf2d3754995166f21f7d2cd2f70b883d471.zlogene@gentoo \
--to=zlogene@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