From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: gnome-extra/gnome-shell-extension-gsconnect/
Date: Sat, 28 May 2022 01:27:09 +0000 (UTC) [thread overview]
Message-ID: <1653701206.61f6ea044a04eb803ae11c0f4e0494eedd930eb0.sam@gentoo> (raw)
commit: 61f6ea044a04eb803ae11c0f4e0494eedd930eb0
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat May 28 01:26:46 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat May 28 01:26:46 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=61f6ea04
gnome-extra/gnome-shell-extension-gsconnect: Stabilize 50 x86, #843794
Signed-off-by: Sam James <sam <AT> gentoo.org>
.../gnome-shell-extension-gsconnect-50.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gnome-extra/gnome-shell-extension-gsconnect/gnome-shell-extension-gsconnect-50.ebuild b/gnome-extra/gnome-shell-extension-gsconnect/gnome-shell-extension-gsconnect-50.ebuild
index f969c402d472..18fec91712f8 100644
--- a/gnome-extra/gnome-shell-extension-gsconnect/gnome-shell-extension-gsconnect-50.ebuild
+++ b/gnome-extra/gnome-shell-extension-gsconnect/gnome-shell-extension-gsconnect-50.ebuild
@@ -10,7 +10,7 @@ SRC_URI="https://github.com/GSConnect/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz
LICENSE="GPL-2+"
SLOT="0"
-KEYWORDS="amd64 ~x86"
+KEYWORDS="amd64 x86"
IUSE="nautilus"
COMMON_DEPEND="dev-libs/glib:2"
next reply other threads:[~2022-05-28 1:27 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-28 1:27 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-09 18:58 [gentoo-commits] repo/gentoo:master commit in: gnome-extra/gnome-shell-extension-gsconnect/ Mart Raudsepp
2024-03-02 23:30 Sam James
2024-03-02 22:51 Mart Raudsepp
2024-02-18 6:08 Arthur Zamarin
2024-01-08 17:27 Sam James
2023-11-10 16:20 Pacho Ramos
2023-10-08 13:52 Pacho Ramos
2023-05-17 22:29 Matt Turner
2023-05-05 10:24 Pacho Ramos
2023-03-26 16:53 Pacho Ramos
2023-03-26 16:53 Pacho Ramos
2023-01-22 11:29 Pacho Ramos
2022-12-19 16:32 Pacho Ramos
2022-12-19 16:30 Pacho Ramos
2022-12-16 20:37 Arthur Zamarin
2022-11-24 8:04 Pacho Ramos
2022-09-19 21:58 Georgy Yakovlev
2022-05-31 18:52 Matt Turner
2022-05-28 1:20 Sam James
2022-03-27 9:23 Pacho Ramos
2022-03-27 9:20 Pacho Ramos
2022-03-08 9:35 Sam James
2021-10-19 21:04 Pacho Ramos
2021-08-25 15:35 Pacho Ramos
2021-07-08 12:51 Pacho Ramos
2021-06-22 16:43 Pacho Ramos
2021-05-31 2:23 Matt Turner
2021-05-30 20:52 Pacho Ramos
2021-05-20 12:37 Pacho Ramos
2021-05-20 12:37 Pacho Ramos
2021-05-20 12:37 Pacho Ramos
2021-04-04 17:14 Pacho Ramos
2021-03-28 19:38 Pacho Ramos
2021-03-14 14:46 Pacho Ramos
2021-03-14 14:46 Pacho Ramos
2021-03-14 14:46 Pacho Ramos
2020-12-01 22:15 Pacho Ramos
2020-12-01 22:15 Pacho Ramos
2020-09-20 9:24 Pacho Ramos
2020-08-30 20:20 Pacho Ramos
2020-08-17 10:08 Pacho Ramos
2020-08-17 10:08 Pacho Ramos
2020-08-15 9:59 Pacho Ramos
2020-07-15 8:22 Pacho Ramos
2020-05-31 12:42 Pacho Ramos
2020-04-22 21:00 Pacho Ramos
2020-03-11 16:38 Pacho Ramos
2019-12-15 13:18 Pacho Ramos
2019-12-15 13:18 Pacho Ramos
2019-12-14 23:05 Pacho Ramos
2019-11-10 12:36 Pacho Ramos
2019-11-10 12:36 Pacho Ramos
2019-10-20 10:14 Pacho Ramos
2019-10-20 10:14 Pacho Ramos
2019-10-20 10:14 Pacho Ramos
2019-09-14 21:01 Pacho Ramos
2019-08-15 17:54 Pacho Ramos
2019-06-09 11:06 Pacho Ramos
2019-06-09 11:06 Pacho Ramos
2019-05-17 17:27 Pacho Ramos
2019-05-17 17:27 Pacho Ramos
2019-05-09 8:14 Pacho Ramos
2019-05-09 8:14 Pacho Ramos
2019-05-03 8:56 Pacho Ramos
2019-04-13 7:16 Pacho Ramos
2019-03-23 13:48 Pacho Ramos
2019-03-23 13:48 Pacho Ramos
2019-03-09 11:29 Pacho Ramos
2019-01-05 13:24 Pacho Ramos
2018-10-21 8:59 Pacho Ramos
2018-10-21 8:59 Pacho Ramos
2018-09-15 10:39 Pacho Ramos
2018-07-25 9:21 Pacho Ramos
2018-07-24 16:10 Pacho Ramos
2018-07-24 16:08 Pacho Ramos
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=1653701206.61f6ea044a04eb803ae11c0f4e0494eedd930eb0.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