public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-qt/qtshadertools/
Date: Fri, 15 Sep 2023 04:49:06 +0000 (UTC)	[thread overview]
Message-ID: <1694753256.321ad9079800bd8b8bbcffd84891d9ce7dc7f374.sam@gentoo> (raw)

commit:     321ad9079800bd8b8bbcffd84891d9ce7dc7f374
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Sep 15 04:47:36 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Sep 15 04:47:36 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=321ad907

dev-qt/qtshadertools: Stabilize 6.5.2 amd64, #914113

Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-qt/qtshadertools/qtshadertools-6.5.2.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-qt/qtshadertools/qtshadertools-6.5.2.ebuild b/dev-qt/qtshadertools/qtshadertools-6.5.2.ebuild
index 174c66ce198a..03c1664487ae 100644
--- a/dev-qt/qtshadertools/qtshadertools-6.5.2.ebuild
+++ b/dev-qt/qtshadertools/qtshadertools-6.5.2.ebuild
@@ -8,7 +8,7 @@ inherit qt6-build
 DESCRIPTION="Qt APIs and Tools for Graphics Pipelines"
 
 if [[ ${QT6_BUILD_TYPE} == release ]]; then
-	KEYWORDS="~amd64 ~arm ~arm64 ~x86"
+	KEYWORDS="amd64 ~arm ~arm64 ~x86"
 fi
 
 RDEPEND="


             reply	other threads:[~2023-09-15  4:49 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-15  4:49 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-08  5:03 [gentoo-commits] repo/gentoo:master commit in: dev-qt/qtshadertools/ Ionen Wolkens
2024-09-27  7:26 Ionen Wolkens
2024-09-24  9:57 Ionen Wolkens
2024-07-16  1:29 Ionen Wolkens
2024-07-08 16:40 Arthur Zamarin
2024-07-08 10:09 Sam James
2024-06-18 18:14 Ionen Wolkens
2024-06-08 13:41 Ionen Wolkens
2024-06-04 19:36 Ionen Wolkens
2024-06-02  4:04 Sam James
2024-05-20  8:48 Ionen Wolkens
2024-04-19  7:55 Ionen Wolkens
2024-04-02 13:06 Ionen Wolkens
2024-04-02  6:09 Arthur Zamarin
2024-03-30  0:29 Ionen Wolkens
2024-03-26  7:10 Ionen Wolkens
2024-03-24 18:39 Ionen Wolkens
2024-03-22 10:29 Ionen Wolkens
2024-03-22  6:16 Arthur Zamarin
2024-03-12 12:01 Ionen Wolkens
2024-02-14 12:24 Ionen Wolkens
2023-12-19 20:33 Ionen Wolkens
2023-12-12 21:25 Ionen Wolkens
2023-12-01 19:48 Jakov Smolić
2023-12-01  6:21 Sam James
2023-12-01  6:21 Sam James
2023-11-29 22:33 Sam James
2023-11-27  8:47 Ionen Wolkens
2023-11-15 19:28 Ionen Wolkens
2023-10-10 14:51 Ionen Wolkens
2023-09-28 13:07 Ionen Wolkens
2023-09-26 19:48 Ionen Wolkens
2023-09-24 17:09 WANG Xuerui
2023-09-24 17:09 WANG Xuerui
2023-09-22 20:53 Sam James
2023-09-12  1:28 Sam James
2023-09-12  1:26 Sam James
2023-09-11 22:59 Sam James
2023-07-26 13:31 Jimi Huotari
2023-07-20 19:41 Jimi Huotari
2023-06-10 13:33 Jimi Huotari
2023-05-06 11:26 Jimi Huotari
2023-04-15 18:39 Jimi Huotari
2023-03-26 16:59 Jimi Huotari
2023-03-19 13:09 Jimi Huotari
2023-02-09 10:02 Andreas Sturmlechner
2023-01-05 22:39 Jimi Huotari
2022-12-01 19:19 Andreas Sturmlechner
2022-09-24 14:32 Andreas Sturmlechner
2022-09-24 14:32 Andreas Sturmlechner
2022-08-02 22:00 Sam James
2022-08-02 21:51 Sam James

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=1694753256.321ad9079800bd8b8bbcffd84891d9ce7dc7f374.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