From: "Yixun Lan" <dlan@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: x11-libs/libwnck/
Date: Tue, 25 May 2021 14:21:11 +0000 (UTC) [thread overview]
Message-ID: <1621952396.9dfe01a857246d73e96e1909127fcd961e3de06c.dlan@gentoo> (raw)
commit: 9dfe01a857246d73e96e1909127fcd961e3de06c
Author: Yixun Lan <dlan <AT> gentoo <DOT> org>
AuthorDate: Tue May 25 13:38:48 2021 +0000
Commit: Yixun Lan <dlan <AT> gentoo <DOT> org>
CommitDate: Tue May 25 14:19:56 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9dfe01a8
x11-libs/libwnck: add riscv keyword
Package-Manager: Portage-3.0.18, Repoman-3.0.3
Signed-off-by: Yixun Lan <dlan <AT> gentoo.org>
x11-libs/libwnck/libwnck-3.36.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/x11-libs/libwnck/libwnck-3.36.0.ebuild b/x11-libs/libwnck/libwnck-3.36.0.ebuild
index b9e56fce571..2600377be1e 100644
--- a/x11-libs/libwnck/libwnck-3.36.0.ebuild
+++ b/x11-libs/libwnck/libwnck-3.36.0.ebuild
@@ -10,7 +10,7 @@ HOMEPAGE="https://developer.gnome.org/libwnck/stable/"
LICENSE="LGPL-2+"
SLOT="3"
-KEYWORDS="~alpha amd64 arm arm64 ~hppa ~ia64 ~mips ppc ppc64 sparc x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-solaris ~x86-solaris"
+KEYWORDS="~alpha amd64 arm arm64 ~hppa ~ia64 ~mips ppc ppc64 ~riscv sparc x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-solaris ~x86-solaris"
IUSE="gtk-doc +introspection startup-notification tools"
next reply other threads:[~2021-05-25 14:21 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 14:21 Yixun Lan [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-20 17:32 [gentoo-commits] repo/gentoo:master commit in: x11-libs/libwnck/ Matt Turner
2023-01-13 12:59 Arthur Zamarin
2022-12-27 8:41 Sam James
2022-12-27 8:41 Sam James
2022-12-27 7:29 Sam James
2022-12-27 7:29 Sam James
2022-12-26 19:52 Arthur Zamarin
2022-12-26 19:52 Arthur Zamarin
2022-12-04 3:03 Matt Turner
2022-12-04 2:41 Matt Turner
2022-11-05 18:58 Arthur Zamarin
2022-11-05 9:58 Arthur Zamarin
2022-11-05 9:44 Arthur Zamarin
2022-10-31 20:31 Matt Turner
2022-09-30 18:53 Matt Turner
2022-03-18 19:24 Matt Turner
2022-03-15 20:54 Matt Turner
2022-03-09 15:39 Sam James
2022-03-09 12:49 Sam James
2022-03-08 12:32 Sam James
2022-02-18 3:44 Matt Turner
2022-01-17 23:19 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-15 0:13 Sam James
2021-04-14 22:07 Sam James
2021-04-14 22:07 Sam James
2021-04-14 18:51 Mikle Kolyada
2021-03-07 2:02 Matt Turner
2021-03-05 22:20 Sam James
2020-11-07 15:23 Mart Raudsepp
2020-11-06 15:19 Sam James
2020-11-05 16:16 Sam James
2020-09-11 16:57 Sergei Trofimovich
2020-08-31 2:52 Sam James
2020-08-30 15:17 Thomas Deutschmann
2020-08-07 7:17 Mart Raudsepp
2020-02-09 14:42 Mart Raudsepp
2018-12-28 7:48 Mart Raudsepp
2018-12-28 3:46 Matt Turner
2018-12-05 7:34 Mikle Kolyada
2018-12-05 7:07 Mikle Kolyada
2018-12-04 16:27 Mikle Kolyada
2018-12-02 14:29 Mikle Kolyada
2018-12-02 10:12 Mikle Kolyada
2018-12-01 14:51 Sergei Trofimovich
2018-11-04 14:16 Sergei Trofimovich
2018-10-06 22:37 Mart Raudsepp
2018-09-14 10:25 Mart Raudsepp
2018-03-15 1:50 Mart Raudsepp
2018-03-14 21:41 Sergei Trofimovich
2018-03-14 21:09 Markus Meier
2018-03-06 21:37 Tobias Klausmann
2018-03-04 20:48 Sergei Trofimovich
2018-02-16 20:39 Sergei Trofimovich
2018-01-18 3:01 Mikle Kolyada
2018-01-13 12:13 Sergei Trofimovich
2017-09-18 10:45 Jeroen Roovers
2017-08-15 22:44 Gilles Dartiguelongue
2017-06-19 11:14 Alexis Ballier
2017-06-17 20:29 Anthony G. Basile
2017-01-30 19:12 Fabian Groffen
2017-01-29 21:11 Fabian Groffen
2017-01-26 10:56 Mart Raudsepp
2016-12-06 20:50 Markus Meier
2016-07-03 16:33 Pacho Ramos
2016-06-28 20:30 Pacho Ramos
2016-05-03 20:57 Markus Meier
2016-04-07 10:19 Jeroen Roovers
2016-03-06 20:52 Mikle Kolyada
2016-02-21 23:44 Pacho Ramos
2016-02-20 13:55 Pacho Ramos
2016-02-20 13:55 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=1621952396.9dfe01a857246d73e96e1909127fcd961e3de06c.dlan@gentoo \
--to=dlan@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