From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: gnome-extra/gnome-shell-frippery/
Date: Thu, 30 May 2024 15:20:58 +0000 (UTC) [thread overview]
Message-ID: <1717082436.69bd5ed8975b05e07b3e1fc4e63c695c3475de0a.arthurzam@gentoo> (raw)
commit: 69bd5ed8975b05e07b3e1fc4e63c695c3475de0a
Author: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Thu May 30 15:20:36 2024 +0000
Commit: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Thu May 30 15:20:36 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=69bd5ed8
gnome-extra/gnome-shell-frippery: Stabilize 45.1 amd64, #928778
Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>
| 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--git a/gnome-extra/gnome-shell-frippery/gnome-shell-frippery-45.1.ebuild b/gnome-extra/gnome-shell-frippery/gnome-shell-frippery-45.1.ebuild
index 8a9221f2ea7c..2d517969355e 100644
--- a/gnome-extra/gnome-shell-frippery/gnome-shell-frippery-45.1.ebuild
+++ b/gnome-extra/gnome-shell-frippery/gnome-shell-frippery-45.1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2023 Gentoo Authors
+# Copyright 1999-2024 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=8
@@ -10,7 +10,7 @@ S="${WORKDIR}/.local/share/gnome-shell"
LICENSE="GPL-2+"
SLOT="0"
-KEYWORDS="~amd64 ~x86"
+KEYWORDS="amd64 ~x86"
RDEPEND="
app-eselect/eselect-gnome-shell-extensions
next reply other threads:[~2024-05-30 15:21 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 15:20 Arthur Zamarin [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-26 19:33 [gentoo-commits] repo/gentoo:master commit in: gnome-extra/gnome-shell-frippery/ Sam James
2024-11-08 16:32 Pacho Ramos
2024-10-08 16:33 Andreas Sturmlechner
2024-05-30 15:20 Arthur Zamarin
2024-03-02 22:51 Mart Raudsepp
2024-02-18 6:08 Arthur Zamarin
2024-01-08 17:27 Sam James
2023-12-28 12:03 Pacho Ramos
2023-12-28 12:03 Pacho Ramos
2023-10-26 15:09 Pacho Ramos
2023-08-12 19:43 Arthur Zamarin
2023-08-02 17:00 Sam James
2023-07-16 20:31 Matt Turner
2023-06-15 14:09 Matt Turner
2023-05-04 18:47 Arthur Zamarin
2023-05-04 18:47 Arthur Zamarin
2023-04-24 16:41 Matt Turner
2022-07-16 21:28 Matt Turner
2022-05-31 18:04 Matt Turner
2022-04-01 17:51 Matt Turner
2022-03-25 18:25 Matt Turner
2022-03-08 9:35 Sam James
2021-10-11 10:51 Mart Raudsepp
2021-10-11 10:51 Mart Raudsepp
2021-07-26 7:15 Matt Turner
2021-07-08 17:35 Matt Turner
2021-07-04 18:24 Matt Turner
2021-05-29 9:02 Sam James
2021-05-29 6:09 Sam James
2021-04-14 20:45 Matt Turner
2021-01-23 22:38 Pacho Ramos
2020-03-01 16:37 Mart Raudsepp
2019-12-23 22:02 Mart Raudsepp
2019-09-06 21:47 Mart Raudsepp
2019-09-06 21:47 Mart Raudsepp
2019-05-18 21:24 Mart Raudsepp
2019-03-30 22:33 Mart Raudsepp
2019-02-27 23:57 Mart Raudsepp
2018-09-30 0:19 Mart Raudsepp
2018-04-29 0:08 Mart Raudsepp
2018-04-26 17:15 Thomas Deutschmann
2018-02-08 8:26 Gilles Dartiguelongue
2018-02-08 8:26 Gilles Dartiguelongue
2016-06-25 18:43 Pacho Ramos
2016-06-25 18:43 Pacho Ramos
2016-03-06 18:58 Mikle Kolyada
2016-01-11 14:26 Pacho Ramos
2015-11-15 22:30 Pacho Ramos
2015-11-15 22:30 Pacho Ramos
2015-09-07 21:11 Mikle Kolyada
2015-09-05 16:56 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=1717082436.69bd5ed8975b05e07b3e1fc4e63c695c3475de0a.arthurzam@gentoo \
--to=arthurzam@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