public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jakov Smolić" <jsmolic@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: kde-frameworks/networkmanager-qt/
Date: Wed, 23 Nov 2022 17:49:05 +0000 (UTC)	[thread overview]
Message-ID: <1669225696.49f36724a9a9be5bbabef259cc68255c6c99170e.jsmolic@gentoo> (raw)

commit:     49f36724a9a9be5bbabef259cc68255c6c99170e
Author:     Jakov Smolić <jsmolic <AT> gentoo <DOT> org>
AuthorDate: Wed Nov 23 17:45:36 2022 +0000
Commit:     Jakov Smolić <jsmolic <AT> gentoo <DOT> org>
CommitDate: Wed Nov 23 17:48:16 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=49f36724

kde-frameworks/networkmanager-qt: Stabilize 5.99.0 amd64, #876484

Signed-off-by: Jakov Smolić <jsmolic <AT> gentoo.org>

 kde-frameworks/networkmanager-qt/networkmanager-qt-5.99.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kde-frameworks/networkmanager-qt/networkmanager-qt-5.99.0.ebuild b/kde-frameworks/networkmanager-qt/networkmanager-qt-5.99.0.ebuild
index 0f87db5a8c7e..fef74c9e325e 100644
--- a/kde-frameworks/networkmanager-qt/networkmanager-qt-5.99.0.ebuild
+++ b/kde-frameworks/networkmanager-qt/networkmanager-qt-5.99.0.ebuild
@@ -9,7 +9,7 @@ inherit ecm frameworks.kde.org
 DESCRIPTION="NetworkManager bindings for Qt"
 
 LICENSE="LGPL-2"
-KEYWORDS="~amd64 ~arm arm64 ~loong ~ppc64 ~riscv ~x86"
+KEYWORDS="amd64 ~arm arm64 ~loong ~ppc64 ~riscv ~x86"
 IUSE="teamd"
 
 DEPEND="


             reply	other threads:[~2022-11-23 17:49 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-23 17:49 Jakov Smolić [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-19 15:03 [gentoo-commits] repo/gentoo:master commit in: kde-frameworks/networkmanager-qt/ Andreas Sturmlechner
2024-06-19 15:03 Andreas Sturmlechner
2024-05-28  2:10 Sam James
2024-05-27 23:47 Sam James
2024-03-01 16:24 Arthur Zamarin
2024-02-28 18:51 Arthur Zamarin
2024-02-19 16:28 Sam James
2024-01-04 10:11 Sam James
2023-12-28 18:55 Arthur Zamarin
2023-08-26  4:50 Sam James
2023-08-02 17:48 Sam James
2023-07-25 18:14 Arthur Zamarin
2023-06-22 19:59 Arthur Zamarin
2023-05-27 13:44 Arthur Zamarin
2023-02-18 16:06 Arthur Zamarin
2023-02-18 13:27 Arthur Zamarin
2022-11-25  1:06 Jakov Smolić
2022-11-12 14:53 Arthur Zamarin
2022-08-06  4:08 Sam James
2022-06-29  7:21 WANG Xuerui
2022-04-29  3:30 Sam James
2022-04-22  1:59 Sam James
2022-04-22  1:57 Sam James
2022-02-10  0:40 Sam James
2022-02-08 14:46 Agostino Sarubbo
2022-02-08 11:02 Jakov Smolić
2021-12-10 18:37 Jakov Smolić
2021-12-10 11:15 Jakov Smolić
2021-09-14  5:19 Sam James
2021-09-13  8:18 Agostino Sarubbo
2021-09-12 23:34 Sam James
2021-08-25 20:07 Yixun Lan
2021-04-11 12:25 Mikle Kolyada
2021-04-11 12:20 Mikle Kolyada
2021-04-10 23:41 Thomas Deutschmann
2020-10-08 19:15 Mikle Kolyada
2020-07-11 15:37 Andreas Sturmlechner
2020-05-31 15:54 Mikle Kolyada
2020-05-30 13:38 Mikle Kolyada
2020-05-30 13:33 Mikle Kolyada
2020-03-01  7:28 Mikle Kolyada
2020-03-01  7:23 Mikle Kolyada
2020-03-01  7:18 Mikle Kolyada
2019-07-28 19:16 Aaron Bauman
2019-07-28  0:36 Mikle Kolyada
2019-07-28  0:15 Mikle Kolyada
2019-05-27 21:04 Aaron Bauman
2019-05-16 12:28 Mikle Kolyada
2019-05-16 12:23 Mikle Kolyada
2019-02-26 20:54 Andreas Sturmlechner
2019-02-06 11:37 Mikle Kolyada
2019-02-06 10:59 Mikle Kolyada
2018-12-22 14:03 Andreas Sturmlechner
2018-10-10 12:23 Mikle Kolyada
2018-10-10  3:01 Thomas Deutschmann
2018-02-08 21:35 Andreas Sturmlechner
2018-01-21 13:24 Michael Palimaka
2017-12-31 18:00 Andreas Sturmlechner
2017-12-31 18:00 Andreas Sturmlechner
2017-07-17 14:15 Michael Palimaka
2017-06-09 10:19 Agostino Sarubbo
2017-06-04 16:00 Agostino Sarubbo
2017-05-28 16:48 Andreas Sturmlechner
2017-01-20  9:47 Agostino Sarubbo
2016-10-12 18:12 Michael Palimaka
2016-10-08 16:20 Michael Palimaka
2016-10-05 18:27 Michael Palimaka

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=1669225696.49f36724a9a9be5bbabef259cc68255c6c99170e.jsmolic@gentoo \
    --to=jsmolic@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