public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-portage/cpuid2cpuflags/
Date: Sat,  4 Mar 2017 18:53:43 +0000 (UTC)	[thread overview]
Message-ID: <1488653607.a4367e33b11c0427f947cda49cc77e6f61bbcb89.mgorny@gentoo> (raw)

commit:     a4367e33b11c0427f947cda49cc77e6f61bbcb89
Author:     Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sat Mar  4 18:48:59 2017 +0000
Commit:     Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sat Mar  4 18:53:27 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a4367e33

app-portage/cpuid2cpuflags: Add a live ebuild

 .../cpuid2cpuflags/cpuid2cpuflags-9999.ebuild       | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/app-portage/cpuid2cpuflags/cpuid2cpuflags-9999.ebuild b/app-portage/cpuid2cpuflags/cpuid2cpuflags-9999.ebuild
new file mode 100644
index 00000000000..8e891b478ae
--- /dev/null
+++ b/app-portage/cpuid2cpuflags/cpuid2cpuflags-9999.ebuild
@@ -0,0 +1,21 @@
+# Copyright 1999-2017 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=6
+
+EGIT_REPO_URI="https://github.com/mgorny/cpuid2cpuflags"
+inherit autotools git-r3
+
+DESCRIPTION="Tool to guess CPU_FLAGS_X86 flags for the host"
+HOMEPAGE="https://github.com/mgorny/cpuid2cpuflags"
+SRC_URI=""
+
+LICENSE="BSD-2"
+SLOT="0"
+KEYWORDS=""
+IUSE=""
+
+src_prepare() {
+	default
+	eautoreconf
+}


             reply	other threads:[~2017-03-04 18:53 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-04 18:53 Michał Górny [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-03-23 19:23 [gentoo-commits] repo/gentoo:master commit in: app-portage/cpuid2cpuflags/ Michał Górny
2017-03-25 14:43 Agostino Sarubbo
2017-03-31 21:45 Michał Górny
2017-04-01  6:15 Michał Górny
2017-04-01  6:15 Michał Górny
2017-04-18  9:25 Alexis Ballier
2017-12-02  9:36 Michał Górny
2017-12-02  9:36 Michał Górny
2018-02-06 15:10 Thomas Deutschmann
2018-03-15 16:17 Mikle Kolyada
2019-01-12 15:38 Michał Górny
2019-07-19 18:15 Michał Górny
2019-09-08 19:15 Thomas Deutschmann
2019-09-09  5:54 Agostino Sarubbo
2019-09-10 20:03 Michał Górny
2019-09-11 10:19 Georgy Yakovlev
2019-09-13 17:58 Mikle Kolyada
2019-09-17 21:00 Michał Górny
2019-12-13 16:57 Michał Górny
2019-12-15 13:43 Agostino Sarubbo
2019-12-15 14:46 Agostino Sarubbo
2019-12-24 14:21 Mikle Kolyada
2019-12-26 11:27 Michał Górny
2020-03-16  2:31 Georgy Yakovlev
2020-04-20 12:32 Michał Górny
2020-04-20 16:40 Georgy Yakovlev
2020-04-21 10:13 Mart Raudsepp
2020-04-22 13:57 Mikle Kolyada
2020-04-23  6:21 Agostino Sarubbo
2020-04-23  6:24 Agostino Sarubbo
2020-04-23  6:29 Agostino Sarubbo
2020-05-04  9:37 Michał Górny
2020-06-08 10:48 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-07-13 17:18 Michał Górny
2020-08-02 14:00 Michał Górny
2020-09-13 19:03 Sam James
2020-09-14  2:48 Sam James
2020-09-18  7:29 Agostino Sarubbo
2020-09-18  7:54 Agostino Sarubbo
2020-09-18  8:26 Agostino Sarubbo
2021-01-06 13:23 Fabian Groffen
2022-05-20  4:42 Michał Górny
2022-05-20  4:42 Michał Górny
2022-07-26  1:36 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  7:05 Sam James
2022-07-26  7:24 Michał Górny
2022-08-10 14:20 Michał Górny
2024-01-02 16:54 Michał Górny
2024-01-22 14:08 Michał Górny
2024-02-08 14:43 Michał Górny
2024-02-08 14:43 Michał Górny
2024-02-08 14:48 Michał Górny
2024-02-08 15:28 Michał Górny
2024-02-08 17:10 Arthur Zamarin
2024-02-22 20:33 Arthur Zamarin
2024-02-23  3:40 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=1488653607.a4367e33b11c0427f947cda49cc77e6f61bbcb89.mgorny@gentoo \
    --to=mgorny@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