From: "Mart Raudsepp" <leio@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: gnome-base/gnome-light/
Date: Sat, 8 Apr 2017 18:26:44 +0000 (UTC) [thread overview]
Message-ID: <1491675966.f2acc4064e59b39f37d9473ecf472a8ab3fa82b0.leio@gentoo> (raw)
commit: f2acc4064e59b39f37d9473ecf472a8ab3fa82b0
Author: Mart Raudsepp <leio <AT> gentoo <DOT> org>
AuthorDate: Sat Apr 8 16:11:11 2017 +0000
Commit: Mart Raudsepp <leio <AT> gentoo <DOT> org>
CommitDate: Sat Apr 8 18:26:06 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f2acc406
gnome-base/gnome-light-3.22.2: amd64 stable
Seems to have been missed out during stabilization run, but gnome-3.22.2 meta is
done and gnome-light here is just a meta too, so just self-stabilize ALLARCHES
Thanks-to: Matt Turner <mattst88 <AT> gentoo.org>
gnome-base/gnome-light/gnome-light-3.22.2.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gnome-base/gnome-light/gnome-light-3.22.2.ebuild b/gnome-base/gnome-light/gnome-light-3.22.2.ebuild
index 36578519b40..3ddd9adfb6d 100644
--- a/gnome-base/gnome-light/gnome-light-3.22.2.ebuild
+++ b/gnome-base/gnome-light/gnome-light-3.22.2.ebuild
@@ -15,7 +15,7 @@ IUSE="cups +gnome-shell"
# when unmasking for an arch
# double check none of the deps are still masked !
-KEYWORDS="~amd64 x86"
+KEYWORDS="amd64 x86"
# XXX: Note to developers:
# This is a wrapper for the 'light' GNOME 3 desktop, and should only consist of
next reply other threads:[~2017-04-08 18:26 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-08 18:26 Mart Raudsepp [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-06 7:09 [gentoo-commits] repo/gentoo:master commit in: gnome-base/gnome-light/ Mart Raudsepp
2024-05-01 5:28 Joonas Niilola
2024-03-02 23:30 Sam James
2023-12-24 14:38 Mart Raudsepp
2023-12-18 23:44 Mart Raudsepp
2023-12-18 23:44 Mart Raudsepp
2023-12-18 23:44 Mart Raudsepp
2023-10-03 7:09 Mart Raudsepp
2021-08-27 15:19 Yixun Lan
2021-05-29 6:09 Sam James
2021-05-15 1:59 Sam James
2021-05-12 22:10 Matt Turner
2020-08-30 18:09 Sam James
2020-04-14 7:08 Sergei Trofimovich
2020-03-29 17:56 Mart Raudsepp
2020-03-29 17:56 Mart Raudsepp
2020-03-29 17:56 Mart Raudsepp
2019-11-30 21:17 Sergei Trofimovich
2019-09-28 20:29 Mart Raudsepp
2019-09-28 20:17 Mart Raudsepp
2019-05-18 20:46 Mart Raudsepp
2019-03-30 21:56 Mart Raudsepp
2019-03-05 19:06 Mart Raudsepp
2019-02-17 15:56 Mikle Kolyada
2019-01-16 1:00 Mart Raudsepp
2018-11-18 9:55 Mikle Kolyada
2018-02-03 20:56 Mart Raudsepp
2018-01-18 3:42 Mikle Kolyada
2018-01-10 6:12 Mart Raudsepp
2017-11-02 0:08 Mart Raudsepp
2017-09-30 6:31 Sergei Trofimovich
2017-09-30 6:31 Sergei Trofimovich
2017-09-23 20:35 Sergei Trofimovich
2017-09-23 20:35 Sergei Trofimovich
2017-08-15 22:44 Gilles Dartiguelongue
2017-06-17 8:39 Sergei Trofimovich
2017-03-25 14:06 Mart Raudsepp
2017-02-04 14:47 Pacho Ramos
2016-11-12 10:30 Gilles Dartiguelongue
2016-11-12 10:30 Gilles Dartiguelongue
2016-11-12 0:37 Gilles Dartiguelongue
2016-11-12 0:37 Gilles Dartiguelongue
2016-09-05 22:37 Gilles Dartiguelongue
2016-03-06 18:20 Mikle Kolyada
2016-01-04 22:12 Gilles Dartiguelongue
2016-01-04 22:12 Gilles Dartiguelongue
2015-12-06 23:41 Gilles Dartiguelongue
2015-09-07 19:58 Mikle Kolyada
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=1491675966.f2acc4064e59b39f37d9473ecf472a8ab3fa82b0.leio@gentoo \
--to=leio@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