From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/intel_clc/
Date: Sun, 1 Sep 2024 02:18:10 +0000 (UTC) [thread overview]
Message-ID: <1725157024.fd75b73ec25a24cdc699d153c1f9fabb997b9db7.sam@gentoo> (raw)
commit: fd75b73ec25a24cdc699d153c1f9fabb997b9db7
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Sep 1 02:17:04 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Sep 1 02:17:04 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fd75b73e
dev-util/intel_clc: Stabilize 24.1.6 amd64, #938854
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-util/intel_clc/intel_clc-24.1.6.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-util/intel_clc/intel_clc-24.1.6.ebuild b/dev-util/intel_clc/intel_clc-24.1.6.ebuild
index df38191345d0..40ac06697204 100644
--- a/dev-util/intel_clc/intel_clc-24.1.6.ebuild
+++ b/dev-util/intel_clc/intel_clc-24.1.6.ebuild
@@ -20,7 +20,7 @@ if [[ ${PV} == 9999 ]]; then
else
S="${WORKDIR}/mesa-${MY_PV}"
SRC_URI="https://archive.mesa3d.org/mesa-${MY_PV}.tar.xz"
- KEYWORDS="~amd64 ~x86"
+ KEYWORDS="amd64 ~x86"
fi
LICENSE="MIT SGI-B-2.0"
next reply other threads:[~2024-09-01 2:18 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-01 2:18 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-22 2:39 [gentoo-commits] repo/gentoo:master commit in: dev-util/intel_clc/ Matt Turner
2024-12-17 3:58 Matt Turner
2024-12-17 3:58 Matt Turner
2024-12-11 17:26 Matt Turner
2024-12-02 16:38 Matt Turner
2024-11-21 17:36 Matt Turner
2024-11-17 4:52 Matt Turner
2024-11-13 18:40 Matt Turner
2024-11-11 0:14 Sam James
2024-11-10 10:00 Sam James
2024-11-01 1:10 Matt Turner
2024-10-18 2:40 Matt Turner
2024-10-03 17:51 Matt Turner
2024-10-03 17:51 Matt Turner
2024-09-18 17:45 Matt Turner
2024-09-18 17:45 Matt Turner
2024-09-18 17:45 Matt Turner
2024-09-06 15:21 Matt Turner
2024-09-02 17:52 Matt Turner
2024-09-02 17:52 Matt Turner
2024-09-01 2:18 Sam James
2024-08-14 21:57 Matt Turner
2024-08-14 21:57 Matt Turner
2024-08-14 21:57 Matt Turner
2024-08-13 14:35 Matt Turner
2024-08-12 15:31 Matt Turner
2024-07-31 16:03 Matt Turner
2024-07-23 5:55 Sam James
2024-07-18 15:07 Matt Turner
2024-07-17 17:16 Sam James
2024-07-17 15:02 Matt Turner
2024-07-17 13:22 Matt Turner
2024-07-11 15:41 Matt Turner
2024-07-08 16:56 Matt Turner
2024-06-19 17:46 Matt Turner
2024-06-06 19:54 Matt Turner
2024-06-05 20:01 Matt Turner
2024-06-04 14:45 Matt Turner
2024-05-22 21:17 Matt Turner
2024-05-22 21:17 Matt Turner
2024-05-22 17:42 Matt Turner
2024-05-15 18:36 Matt Turner
2024-05-15 18:36 Matt Turner
2024-05-15 18:36 Matt Turner
2024-05-08 20:43 Matt Turner
2024-05-08 20:43 Matt Turner
2024-04-25 16:10 Matt Turner
2024-04-24 19:07 Matt Turner
2024-04-10 22:08 Matt Turner
2024-04-04 3:21 Matt Turner
2024-04-02 16:54 Arthur Zamarin
2024-03-27 23:58 Matt Turner
2024-03-21 1:19 Matt Turner
2024-03-14 16:41 Matt Turner
2024-03-05 8:51 Sam James
2024-03-05 5:05 Sam James
2024-03-05 4:52 Sam James
2024-03-01 21:53 Sven Wegener
2024-02-28 20:26 Matt Turner
2024-02-16 14:11 Matt Turner
2024-02-15 14:51 Matt Turner
2024-02-15 14:51 Matt Turner
2024-02-15 4:50 Matt Turner
2024-02-10 10:47 Michał Górny
2024-02-01 19:49 Matt Turner
2024-02-01 19:49 Matt Turner
2024-01-25 3:36 Matt Turner
2024-01-24 17:00 Matt Turner
2024-01-16 18:01 Arthur Zamarin
2024-01-11 4:41 Matt Turner
2024-01-10 15:57 Sam James
2024-01-10 15:54 Matt Turner
2024-01-10 15:50 Sam James
2023-12-28 15:52 Matt Turner
2023-12-28 15:52 Matt Turner
2023-12-14 16:16 Matt Turner
2023-11-29 22:11 Matt Turner
2023-11-28 7:57 Sam James
2023-11-25 17:31 Matt Turner
2023-11-25 5:21 Matt Turner
2023-11-16 4:11 Matt Turner
2023-11-14 18:36 Matt Turner
2023-11-09 18:40 Matt Turner
2023-11-09 18:40 Matt Turner
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=1725157024.fd75b73ec25a24cdc699d153c1f9fabb997b9db7.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