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/qtcharts/
Date: Mon, 23 May 2022 18:55:30 +0000 (UTC)	[thread overview]
Message-ID: <1653332102.e20936cfbb7f90b4033458b3f6ca4fac5d3a9626.sam@gentoo> (raw)

commit:     e20936cfbb7f90b4033458b3f6ca4fac5d3a9626
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon May 23 18:55:02 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon May 23 18:55:02 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e20936cf

dev-qt/qtcharts: Stabilize 5.15.3 ppc, #847019

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

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

diff --git a/dev-qt/qtcharts/qtcharts-5.15.3.ebuild b/dev-qt/qtcharts/qtcharts-5.15.3.ebuild
index 0f505dbcc8d1..06ecdb613ab4 100644
--- a/dev-qt/qtcharts/qtcharts-5.15.3.ebuild
+++ b/dev-qt/qtcharts/qtcharts-5.15.3.ebuild
@@ -9,7 +9,7 @@ DESCRIPTION="Chart component library for the Qt5 framework"
 LICENSE="GPL-3"
 
 if [[ ${QT5_BUILD_TYPE} == release ]]; then
-	KEYWORDS="amd64 ~arm arm64 ~ppc ~ppc64 ~riscv x86"
+	KEYWORDS="amd64 ~arm arm64 ppc ~ppc64 ~riscv x86"
 fi
 
 IUSE="qml"


             reply	other threads:[~2022-05-23 18:55 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23 18:55 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-02 14:10 [gentoo-commits] repo/gentoo:master commit in: dev-qt/qtcharts/ Arthur Zamarin
2024-11-01  6:35 Arthur Zamarin
2024-07-08 16:40 Arthur Zamarin
2024-07-08 11:16 Arthur Zamarin
2024-07-08 10:09 Sam James
2024-06-08  5:27 Arthur Zamarin
2024-06-04 16:16 Arthur Zamarin
2024-05-28 18:56 Arthur Zamarin
2024-04-13 17:50 Arthur Zamarin
2024-04-03 19:06 Arthur Zamarin
2024-04-02  6:09 Arthur Zamarin
2024-04-01 18:29 Arthur Zamarin
2024-03-22  6:16 Arthur Zamarin
2024-02-20 14:30 Arthur Zamarin
2024-02-14 12:24 Ionen Wolkens
2024-01-02 16:26 WANG Xuerui
2023-12-17 18:29 Arthur Zamarin
2023-12-05  7:25 Joonas Niilola
2023-12-03 20:48 Jakov Smolić
2023-12-02 10:57 Arthur Zamarin
2023-12-02 10:57 Arthur Zamarin
2023-12-01 10:58 Arthur Zamarin
2023-12-01 10:58 Arthur Zamarin
2023-11-15 17:20 Arthur Zamarin
2023-11-06  8:15 Arthur Zamarin
2023-10-10 14:51 Ionen Wolkens
2023-09-26 19:48 Ionen Wolkens
2023-09-15  4:49 Sam James
2023-09-15  1:32 Ionen Wolkens
2023-09-05 13:05 Ionen Wolkens
2023-07-26 13:31 Jimi Huotari
2023-07-20 19:41 Jimi Huotari
2023-07-12 23:39 Sam James
2023-06-10 13:33 Jimi Huotari
2023-05-06 11:26 Jimi Huotari
2023-05-01  7:26 Arthur Zamarin
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-05 19:45 Arthur Zamarin
2022-12-04 19:30 Arthur Zamarin
2022-11-16  5:57 WANG Xuerui
2022-07-02 12:54 Arthur Zamarin
2022-07-02 11:02 Arthur Zamarin
2022-06-18 15:39 Sam James
2022-05-23 18:55 Sam James
2022-04-19 16:57 Arthur Zamarin
2022-04-17 19:29 Sam James
2020-01-26 23:56 Georgy Yakovlev

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=1653332102.e20936cfbb7f90b4033458b3f6ca4fac5d3a9626.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