From: "Pacho Ramos" <pacho@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: gnome-extra/gnome-shell-extension-bing-wallpaper/
Date: Sun, 18 Sep 2022 08:33:42 +0000 (UTC) [thread overview]
Message-ID: <1663489630.21a9e15d29a2379f7a205eae7f2073ba0fe4ff91.pacho@gentoo> (raw)
commit: 21a9e15d29a2379f7a205eae7f2073ba0fe4ff91
Author: Pacho Ramos <pacho <AT> gentoo <DOT> org>
AuthorDate: Sun Sep 18 07:25:55 2022 +0000
Commit: Pacho Ramos <pacho <AT> gentoo <DOT> org>
CommitDate: Sun Sep 18 08:27:10 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=21a9e15d
gnome-extra/gnome-shell-extension-bing-wallpaper: stabilize 41 for ALLARCHES
Signed-off-by: Pacho Ramos <pacho <AT> gentoo.org>
.../gnome-shell-extension-bing-wallpaper-41.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gnome-extra/gnome-shell-extension-bing-wallpaper/gnome-shell-extension-bing-wallpaper-41.ebuild b/gnome-extra/gnome-shell-extension-bing-wallpaper/gnome-shell-extension-bing-wallpaper-41.ebuild
index c57276c6cfd2..9d0bf9746e94 100644
--- a/gnome-extra/gnome-shell-extension-bing-wallpaper/gnome-shell-extension-bing-wallpaper-41.ebuild
+++ b/gnome-extra/gnome-shell-extension-bing-wallpaper/gnome-shell-extension-bing-wallpaper-41.ebuild
@@ -10,7 +10,7 @@ SRC_URI="https://github.com/neffo/bing-wallpaper-gnome-extension/archive/v${PV}.
LICENSE="GPL-3"
SLOT="0"
-KEYWORDS="~amd64 ~x86"
+KEYWORDS="amd64 x86"
IUSE=""
RDEPEND="
next reply other threads:[~2022-09-18 8:33 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 8:33 Pacho Ramos [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-29 18:34 [gentoo-commits] repo/gentoo:master commit in: gnome-extra/gnome-shell-extension-bing-wallpaper/ Pacho Ramos
2024-09-29 18:34 Pacho Ramos
2024-07-12 9:05 Pacho Ramos
2024-05-18 10:40 Pacho Ramos
2024-05-18 10:40 Pacho Ramos
2024-05-18 10:40 Pacho Ramos
2024-02-18 6:08 Arthur Zamarin
2024-01-08 17:27 Sam James
2023-11-10 14:16 Pacho Ramos
2023-11-10 14:16 Pacho Ramos
2023-10-26 15:09 Pacho Ramos
2023-10-20 13:14 Pacho Ramos
2023-09-10 8:19 Pacho Ramos
2023-05-05 10:24 Pacho Ramos
2023-04-18 14:17 Pacho Ramos
2023-04-09 18:12 Pacho Ramos
2023-04-09 18:12 Pacho Ramos
2023-02-24 14:48 Pacho Ramos
2023-01-24 17:26 Pacho Ramos
2022-10-02 8:51 Pacho Ramos
2022-10-02 8:51 Pacho Ramos
2022-08-14 12:49 Pacho Ramos
2022-08-14 12:49 Pacho Ramos
2022-05-29 10:23 Pacho Ramos
2022-05-04 15:37 Pacho Ramos
2022-03-26 20:01 Pacho Ramos
2022-03-26 20:01 Pacho Ramos
2022-03-09 21:36 Pacho Ramos
2022-01-07 11:36 Pacho Ramos
2021-12-16 8:32 Pacho Ramos
2021-11-11 10:44 Pacho Ramos
2021-11-11 10:44 Pacho Ramos
2021-10-19 20:33 Pacho Ramos
2021-09-26 16:10 Pacho Ramos
2021-07-08 12:34 Pacho Ramos
2021-06-29 19:10 Pacho Ramos
2021-06-16 9:21 Pacho Ramos
2021-06-06 18:12 Pacho Ramos
2021-05-20 12:37 Pacho Ramos
2021-05-20 12:37 Pacho Ramos
2021-05-20 12:37 Pacho Ramos
2021-05-08 9:27 Pacho Ramos
2021-05-08 9:27 Pacho Ramos
2021-03-28 13:02 Pacho Ramos
2021-03-28 13:02 Pacho Ramos
2021-03-28 10:45 Pacho Ramos
2021-03-14 14:46 Pacho Ramos
2021-03-14 14:46 Pacho Ramos
2021-01-23 15:26 Pacho Ramos
2020-08-30 20:20 Pacho Ramos
2020-08-21 13:00 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=1663489630.21a9e15d29a2379f7a205eae7f2073ba0fe4ff91.pacho@gentoo \
--to=pacho@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