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: gnome-extra/gnome-shell-extension-control-blur-effect-on-lock-screen/
Date: Mon,  8 Jan 2024 17:27:34 +0000 (UTC)	[thread overview]
Message-ID: <1704734778.3179ac49cf3630145c5f3e1c3b2d6fc50ecee9a4.sam@gentoo> (raw)

commit:     3179ac49cf3630145c5f3e1c3b2d6fc50ecee9a4
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Jan  8 17:23:48 2024 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Jan  8 17:26:18 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3179ac49

gnome-extra/gnome-shell-extension-control-blur-effect-on-lock-screen: Stabilize 20230905 amd64, #920697

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

 ...shell-extension-control-blur-effect-on-lock-screen-20230905.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gnome-extra/gnome-shell-extension-control-blur-effect-on-lock-screen/gnome-shell-extension-control-blur-effect-on-lock-screen-20230905.ebuild b/gnome-extra/gnome-shell-extension-control-blur-effect-on-lock-screen/gnome-shell-extension-control-blur-effect-on-lock-screen-20230905.ebuild
index 3f973349faf1..f6f324c717a7 100644
--- a/gnome-extra/gnome-shell-extension-control-blur-effect-on-lock-screen/gnome-shell-extension-control-blur-effect-on-lock-screen-20230905.ebuild
+++ b/gnome-extra/gnome-shell-extension-control-blur-effect-on-lock-screen/gnome-shell-extension-control-blur-effect-on-lock-screen-20230905.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
@@ -11,7 +11,7 @@ SRC_URI="https://github.com/PRATAP-KUMAR/Control_Blur_Effect_On_Lock_Screen/arch
 
 LICENSE="GPL-3+"
 SLOT="0"
-KEYWORDS="~amd64 ~x86"
+KEYWORDS="amd64 ~x86"
 IUSE=""
 
 # glib for glib-compile-schemas at build time, needed at runtime anyways


             reply	other threads:[~2024-01-08 17:27 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08 17:27 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-18  6:08 [gentoo-commits] repo/gentoo:master commit in: gnome-extra/gnome-shell-extension-control-blur-effect-on-lock-screen/ Arthur Zamarin
2023-09-29 11:31 Pacho Ramos
2023-05-05 10:24 Pacho Ramos
2023-04-17 14:52 Pacho Ramos
2023-02-24 14:48 Pacho Ramos
2022-12-16 20:37 Arthur Zamarin
2022-09-18  8:33 Pacho Ramos
2022-05-29 10:23 Pacho Ramos
2022-03-27  9:48 Pacho Ramos
2022-03-27  9:48 Pacho Ramos
2022-03-09 21:36 Pacho Ramos
2022-03-09 21:36 Pacho Ramos
2021-12-21 18:54 Pacho Ramos
2021-12-18 12:41 Pacho Ramos
2021-11-11 11:52 Pacho Ramos
2021-11-11 11:52 Pacho Ramos
2021-08-25 15:35 Pacho Ramos
2021-06-29 19:10 Pacho Ramos
2021-06-14 19:39 Pacho Ramos
2021-06-14 19:39 Pacho Ramos
2021-06-14  9:09 Pacho Ramos
2021-05-30 20:52 Pacho Ramos
2021-05-20 12:37 Pacho Ramos
2021-05-20 12:37 Pacho Ramos
2021-03-14 14:46 Pacho Ramos
2021-03-14 14:46 Pacho Ramos
2021-03-14 14:46 Pacho Ramos
2021-01-23 22:38 Pacho Ramos
2020-12-01 22:15 Pacho Ramos
2020-08-30 20:20 Pacho Ramos
2020-08-30 10:01 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=1704734778.3179ac49cf3630145c5f3e1c3b2d6fc50ecee9a4.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