From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: gnome-base/gnome-session/
Date: Mon, 12 Apr 2021 23:11:46 +0000 (UTC) [thread overview]
Message-ID: <1618268998.7b19ea79d83c7d6a229bc660bd73a52fcbbf1d64.sam@gentoo> (raw)
commit: 7b19ea79d83c7d6a229bc660bd73a52fcbbf1d64
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Apr 12 23:09:58 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Apr 12 23:09:58 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7b19ea79
gnome-base/gnome-session: Stabilize 3.38.0 arm64, #774927
Signed-off-by: Sam James <sam <AT> gentoo.org>
gnome-base/gnome-session/gnome-session-3.38.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gnome-base/gnome-session/gnome-session-3.38.0.ebuild b/gnome-base/gnome-session/gnome-session-3.38.0.ebuild
index 57092bb93e8..8ca32d8859c 100644
--- a/gnome-base/gnome-session/gnome-session-3.38.0.ebuild
+++ b/gnome-base/gnome-session/gnome-session-3.38.0.ebuild
@@ -9,7 +9,7 @@ HOMEPAGE="https://gitlab.gnome.org/GNOME/gnome-session"
LICENSE="GPL-2+"
SLOT="0"
-KEYWORDS="~alpha amd64 ~arm ~arm64 ~ia64 ~ppc ~ppc64 ~sparc x86 ~amd64-linux ~x86-linux ~x86-solaris"
+KEYWORDS="~alpha amd64 ~arm arm64 ~ia64 ~ppc ~ppc64 ~sparc x86 ~amd64-linux ~x86-linux ~x86-solaris"
IUSE="doc elogind systemd"
# There is a null backend available, thus ?? not ^^
REQUIRED_USE="?? ( elogind systemd )"
next reply other threads:[~2021-04-12 23:11 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 23:11 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-03 8:07 [gentoo-commits] repo/gentoo:master commit in: gnome-base/gnome-session/ Pacho Ramos
2024-02-11 8:09 Arthur Zamarin
2023-07-27 5:11 WANG Xuerui
2023-06-03 1:47 Matt Turner
2023-05-02 17:50 Arthur Zamarin
2023-05-02 17:50 Arthur Zamarin
2023-05-02 17:48 Arthur Zamarin
2023-03-20 21:23 Matt Turner
2023-03-12 2:01 Matt Turner
2022-10-30 16:34 Matt Turner
2022-10-01 20:08 Matt Turner
2022-03-23 6:14 Matt Turner
2022-01-13 22:34 Matt Turner
2022-01-13 22:34 Matt Turner
2021-10-31 0:19 Sam James
2021-05-04 20:22 Matt Turner
2021-05-04 20:22 Matt Turner
2021-04-29 1:52 Sam James
2021-04-28 2:41 Matt Turner
2021-04-16 2:16 Matt Turner
2021-04-15 15:36 Matt Turner
2021-04-15 5:25 Sam James
2021-04-15 1:33 Sam James
2021-04-14 18:51 Mikle Kolyada
2020-10-07 17:57 Mikle Kolyada
2020-07-12 21:32 Mart Raudsepp
2020-03-15 17:38 Mart Raudsepp
2019-12-23 21:26 Mart Raudsepp
2019-09-19 18:16 Mart Raudsepp
2019-03-30 22:21 Mart Raudsepp
2019-03-11 18:17 Mart Raudsepp
2019-03-02 14:28 Mart Raudsepp
2018-09-28 13:51 Mart Raudsepp
2018-01-27 8:23 Michał Górny
2018-01-18 3:15 Mikle Kolyada
2017-12-23 2:05 Mart Raudsepp
2017-07-25 13:36 Alexis Ballier
2017-07-25 12:27 Alexis Ballier
2017-04-12 23:05 Mart Raudsepp
2017-03-19 0:00 Mart Raudsepp
2017-03-08 12:11 Mart Raudsepp
2017-01-31 19:43 Johannes Huber
2016-12-30 3:38 Mart Raudsepp
2016-11-12 12:23 Gilles Dartiguelongue
2016-11-11 12:47 Gilles Dartiguelongue
2016-11-11 12:47 Gilles Dartiguelongue
2016-07-12 6:12 Remi Cardona
2016-03-06 17:23 Mikle Kolyada
2015-11-26 10:51 Gilles Dartiguelongue
2015-11-14 19:46 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=1618268998.7b19ea79d83c7d6a229bc660bd73a52fcbbf1d64.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