From: "Thomas Deutschmann" <whissi@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-misc/resolve-march-native/
Date: Tue, 4 Jun 2019 14:45:25 +0000 (UTC) [thread overview]
Message-ID: <1559659449.f31ee8e62e0f08a1215c25131d20f65d4d0d6477.whissi@gentoo> (raw)
commit: f31ee8e62e0f08a1215c25131d20f65d4d0d6477
Author: Thomas Deutschmann <whissi <AT> gentoo <DOT> org>
AuthorDate: Tue Jun 4 14:24:52 2019 +0000
Commit: Thomas Deutschmann <whissi <AT> gentoo <DOT> org>
CommitDate: Tue Jun 4 14:44:09 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f31ee8e6
app-misc/resolve-march-native: x86 stable (bug #687248)
Package-Manager: Portage-2.3.67, Repoman-2.3.14
Signed-off-by: Thomas Deutschmann <whissi <AT> gentoo.org>
app-misc/resolve-march-native/resolve-march-native-0.9.2.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/app-misc/resolve-march-native/resolve-march-native-0.9.2.ebuild b/app-misc/resolve-march-native/resolve-march-native-0.9.2.ebuild
index ed6234409b1..8a89b9b806e 100644
--- a/app-misc/resolve-march-native/resolve-march-native-0.9.2.ebuild
+++ b/app-misc/resolve-march-native/resolve-march-native-0.9.2.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2016 Gentoo Foundation
+# Copyright 1999-2019 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI="5"
@@ -12,7 +12,7 @@ SRC_URI="https://github.com/hartwork/${PN}/archive/${PV}.tar.gz -> ${P}.tar.gz"
LICENSE="GPL-2+"
SLOT="0"
-KEYWORDS="~amd64 ~x86"
+KEYWORDS="~amd64 x86"
IUSE=""
DEPEND="dev-python/setuptools[${PYTHON_USEDEP}]"
next reply other threads:[~2019-06-04 14:45 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 14:45 Thomas Deutschmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-05 0:14 [gentoo-commits] repo/gentoo:master commit in: app-misc/resolve-march-native/ Sebastian Pipping
2024-12-21 3:11 Sam James
2024-12-21 3:11 Sam James
2024-12-21 3:11 Sam James
2024-12-20 19:07 Sebastian Pipping
2024-10-03 15:50 Sebastian Pipping
2024-09-20 19:45 Sebastian Pipping
2024-09-20 19:45 Sebastian Pipping
2024-01-08 21:10 Arthur Zamarin
2024-01-08 21:10 Arthur Zamarin
2024-01-08 7:53 Sam James
2024-01-05 15:51 Sebastian Pipping
2023-12-07 22:11 Sebastian Pipping
2023-12-07 17:50 Sebastian Pipping
2023-12-02 15:06 Sebastian Pipping
2023-11-05 19:42 Sebastian Pipping
2023-11-05 19:42 Sebastian Pipping
2023-11-04 14:15 Sebastian Pipping
2023-04-20 5:01 Sam James
2023-04-20 4:17 Sam James
2023-03-19 23:30 Sebastian Pipping
2022-11-28 20:19 Sebastian Pipping
2022-11-28 20:19 Sebastian Pipping
2022-09-13 16:00 Sebastian Pipping
2022-09-11 21:39 Sebastian Pipping
2022-06-01 8:13 Agostino Sarubbo
2022-06-01 8:09 Agostino Sarubbo
2021-09-20 14:15 Sebastian Pipping
2021-03-13 11:37 Sam James
2021-03-13 11:36 Sam James
2020-10-03 17:17 Sebastian Pipping
2020-09-27 16:22 Sam James
2020-09-19 8:04 Michał Górny
2020-08-30 20:42 Thomas Deutschmann
2020-08-05 13:53 Agostino Sarubbo
2020-05-07 13:18 Michał Górny
2019-10-27 23:02 Sebastian Pipping
2019-10-20 19:13 Sebastian Pipping
2019-06-05 6:48 Agostino Sarubbo
2016-11-20 18:36 Sebastian Pipping
2015-08-23 18:01 Sebastian Pipping
2015-08-21 19:29 Sebastian Pipping
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=1559659449.f31ee8e62e0f08a1215c25131d20f65d4d0d6477.whissi@gentoo \
--to=whissi@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