public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "WANG Xuerui" <xen0n@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: gnome-extra/cinnamon-session/
Date: Tue, 26 Sep 2023 15:59:27 +0000 (UTC)	[thread overview]
Message-ID: <1695743919.93f417f462529083328e2d5e5904631db9c2c5f0.xen0n@gentoo> (raw)

commit:     93f417f462529083328e2d5e5904631db9c2c5f0
Author:     WANG Xuerui <xen0n <AT> gentoo <DOT> org>
AuthorDate: Tue Sep 26 15:38:03 2023 +0000
Commit:     WANG Xuerui <xen0n <AT> gentoo <DOT> org>
CommitDate: Tue Sep 26 15:58:39 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=93f417f4

gnome-extra/cinnamon-session: keyword 5.8.1 for ~loong

Signed-off-by: WANG Xuerui <xen0n <AT> gentoo.org>

 gnome-extra/cinnamon-session/cinnamon-session-5.8.1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gnome-extra/cinnamon-session/cinnamon-session-5.8.1.ebuild b/gnome-extra/cinnamon-session/cinnamon-session-5.8.1.ebuild
index 7b666e938fea..1282203d2a18 100644
--- a/gnome-extra/cinnamon-session/cinnamon-session-5.8.1.ebuild
+++ b/gnome-extra/cinnamon-session/cinnamon-session-5.8.1.ebuild
@@ -13,7 +13,7 @@ SRC_URI="https://github.com/linuxmint/cinnamon-session/archive/${PV}.tar.gz -> $
 
 LICENSE="GPL-2+ LGPL-2+"
 SLOT="0"
-KEYWORDS="~amd64 ~arm64 ~ppc64 ~riscv ~x86"
+KEYWORDS="~amd64 ~arm64 ~loong ~ppc64 ~riscv ~x86"
 IUSE="systemd"
 
 COMMON_DEPEND="


             reply	other threads:[~2023-09-26 15:59 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-26 15:59 WANG Xuerui [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-25 14:22 [gentoo-commits] repo/gentoo:master commit in: gnome-extra/cinnamon-session/ Joonas Niilola
2024-09-25 13:58 Joonas Niilola
2024-08-05  3:36 Eli Schwartz
2024-08-05  3:36 Eli Schwartz
2024-07-01  6:47 Joonas Niilola
2024-07-01  6:47 Joonas Niilola
2024-06-03  6:34 Sam James
2024-05-29 14:43 Jakov Smolić
2024-05-29 11:47 Sam James
2024-02-15 13:29 Joonas Niilola
2023-10-13  7:43 Joonas Niilola
2023-10-04  8:24 Joonas Niilola
2023-07-16 18:34 Sam James
2023-06-03  1:47 Matt Turner
2023-06-03  1:47 Matt Turner
2023-05-07 22:14 Sam James
2023-04-30 16:50 Arthur Zamarin
2023-04-29 18:16 Arthur Zamarin
2022-12-24  7:11 Sam James
2022-11-22  6:20 Sam James
2022-11-22  6:20 Sam James
2022-11-21 17:46 Arthur Zamarin
2022-10-12 23:09 Sam James
2022-10-12 23:09 Sam James
2022-05-11  2:11 Sam James
2022-05-05  3:01 Sam James
2022-05-05  3:01 Sam James
2022-02-18  2:44 Sam James
2022-01-21 17:15 Sam James
2022-01-21 17:15 Sam James
2021-12-24 20:00 Jakov Smolić
2021-12-24 19:25 Jakov Smolić
2021-11-23  1:25 Yixun Lan
2021-07-31  8:36 Joonas Niilola
2021-07-31  8:36 Joonas Niilola
2021-06-12  3:55 Sam James
2021-06-12  3:55 Sam James
2021-06-08  7:34 Sam James
2021-06-01 16:28 Joonas Niilola
2021-06-01 16:28 Joonas Niilola
2021-03-01 13:02 Joonas Niilola
2021-01-24 17:31 Joonas Niilola
2021-01-06  1:05 Sam James
2020-12-29 17:14 Sam James
2020-12-16 22:30 Sam James
2020-09-15 14:20 Joonas Niilola
2020-09-09  2:15 Sam James
2020-05-31 19:05 Matt Turner
2020-05-29  0:11 Matt Turner
2019-06-07 20:12 Mikle Kolyada
2019-06-04 20:58 Thomas Deutschmann
2019-03-17 21:44 Mart Raudsepp
2018-12-05  7:04 Mart Raudsepp
2018-11-28 19:56 Kristian Fiskerstrand
2018-04-12 19:07 Thomas Deutschmann
2018-04-06 14:00 Aaron Bauman
2017-11-28 18:48 Kristian Fiskerstrand
2017-11-28 18:48 Kristian Fiskerstrand
2017-11-28 18:37 Kristian Fiskerstrand
2017-11-26 15:43 Kristian Fiskerstrand
2017-09-05 20:00 Kristian Fiskerstrand
2017-06-24 14:58 Kristian Fiskerstrand
2016-11-22 20:42 Kristian Fiskerstrand
2016-10-01  0:54 Pacho Ramos
2016-09-17 13:29 Kristian Fiskerstrand
2016-05-29 12:42 Pacho Ramos
2016-05-29 12:42 Pacho Ramos
2016-03-06 18:58 Mikle Kolyada
2015-11-15 22:30 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=1695743919.93f417f462529083328e2d5e5904631db9c2c5f0.xen0n@gentoo \
    --to=xen0n@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