public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/opencl-headers/
Date: Sat,  8 Apr 2023 08:30:03 +0000 (UTC)	[thread overview]
Message-ID: <1680942594.7c3f2481411fce55d27a0e058e2b1538e2094acd.arthurzam@gentoo> (raw)

commit:     7c3f2481411fce55d27a0e058e2b1538e2094acd
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Sat Apr  8 08:29:54 2023 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Sat Apr  8 08:29:54 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7c3f2481

dev-util/opencl-headers: Stabilize 2023.02.06 amd64, #903985

Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>

 dev-util/opencl-headers/opencl-headers-2023.02.06.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-util/opencl-headers/opencl-headers-2023.02.06.ebuild b/dev-util/opencl-headers/opencl-headers-2023.02.06.ebuild
index 84f7dd5f1d80..2681b0c73f0a 100644
--- a/dev-util/opencl-headers/opencl-headers-2023.02.06.ebuild
+++ b/dev-util/opencl-headers/opencl-headers-2023.02.06.ebuild
@@ -14,7 +14,7 @@ SRC_URI="https://github.com/KhronosGroup/${MY_PN}/archive/refs/tags/v${PV}.tar.g
 
 LICENSE="Apache-2.0"
 SLOT="0"
-KEYWORDS="~amd64 ~ppc64 ~x86"
+KEYWORDS="amd64 ~ppc64 ~x86"
 IUSE="test"
 
 RESTRICT="!test? ( test )"


             reply	other threads:[~2023-04-08  8:30 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-08  8:30 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-12 13:52 [gentoo-commits] repo/gentoo:master commit in: dev-util/opencl-headers/ Marek Szuba
2024-05-23 13:34 WANG Xuerui
2024-04-24 14:17 Sam James
2024-04-24 14:17 Sam James
2024-04-24 14:13 Sam James
2023-12-24 11:45 Marek Szuba
2023-08-14 10:16 Marek Szuba
2023-07-15  8:19 Arthur Zamarin
2023-07-15  8:19 Arthur Zamarin
2023-07-15  3:10 Sam James
2023-04-21  8:56 Marek Szuba
2023-04-12  6:05 Yixun Lan
2023-04-08 18:49 Marek Szuba
2023-04-08 11:13 Arthur Zamarin
2023-04-08  9:00 Arthur Zamarin
2023-02-24 22:07 Marek Szuba
2023-01-28 22:55 Marek Szuba
2023-01-28  1:40 Sam James
2023-01-28  0:26 Sam James
2023-01-28  0:15 Sam James
2022-10-04  0:53 Marek Szuba
2022-09-26  9:07 Marek Szuba
2022-09-26  1:01 Marek Szuba
2022-09-05 21:57 Marek Szuba
2022-07-26  4:49 Sam James
2022-07-24  1:04 Sam James
2022-06-01 23:43 Marek Szuba
2022-04-11 11:16 Marek Szuba
2022-04-11  6:35 Jakov Smolić
2022-04-10  9:05 Agostino Sarubbo
2022-03-01 16:47 Marek Szuba
2022-02-09  0:20 Marek Szuba
2021-09-29 14:07 Sam James
2021-09-29 14:07 Sam James
2021-08-28 23:11 Marek Szuba
2021-08-28 20:21 Marek Szuba
2021-06-26  9:45 罗百科
2021-06-23  9:15 Marek Szuba
2021-06-23  6:29 Agostino Sarubbo
2021-06-23  4:43 Sam James
2021-05-13 14:27 Marek Szuba
2021-05-06 17:07 Marek Szuba
2021-04-27 11:05 Marek Szuba
2021-03-20  9:02 罗百科
2020-11-12 21:03 Thomas Deutschmann
2020-11-06 20:38 Sam James
2020-06-19 14:31 Marek Szuba
2020-05-14 21:29 Thomas Deutschmann
2020-05-12 12:50 Mikle Kolyada
2020-04-08 22:52 Marek Szuba
2020-04-02  0:21 Marek Szuba

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=1680942594.7c3f2481411fce55d27a0e058e2b1538e2094acd.arthurzam@gentoo \
    --to=arthurzam@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