public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Georgy Yakovlev" <gyakovlev@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-editors/gedit-plugins/
Date: Tue,  4 Jan 2022 22:36:34 +0000 (UTC)	[thread overview]
Message-ID: <1641335573.bbb121d03b7987f20923ed7e8f9d6ed868d5aa6a.gyakovlev@gentoo> (raw)

commit:     bbb121d03b7987f20923ed7e8f9d6ed868d5aa6a
Author:     Georgy Yakovlev <gyakovlev <AT> gentoo <DOT> org>
AuthorDate: Tue Jan  4 22:32:45 2022 +0000
Commit:     Georgy Yakovlev <gyakovlev <AT> gentoo <DOT> org>
CommitDate: Tue Jan  4 22:32:53 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bbb121d0

app-editors/gedit-plugins: keyword 40.1 for ~ppc64

Signed-off-by: Georgy Yakovlev <gyakovlev <AT> gentoo.org>

 app-editors/gedit-plugins/gedit-plugins-40.1.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/app-editors/gedit-plugins/gedit-plugins-40.1.ebuild b/app-editors/gedit-plugins/gedit-plugins-40.1.ebuild
index 83f1ce6c6708..663c00d14205 100644
--- a/app-editors/gedit-plugins/gedit-plugins-40.1.ebuild
+++ b/app-editors/gedit-plugins/gedit-plugins-40.1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2021 Gentoo Authors
+# Copyright 1999-2022 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=7
@@ -12,7 +12,7 @@ DESCRIPTION="Collection of extra plugins for the gedit Text Editor"
 HOMEPAGE="https://wiki.gnome.org/Apps/Gedit/ShippedPlugins"
 
 LICENSE="GPL-2+"
-KEYWORDS="amd64 ~riscv x86"
+KEYWORDS="amd64 ~ppc64 ~riscv x86"
 SLOT="0"
 
 IUSE="charmap git +python terminal vala"


             reply	other threads:[~2022-01-04 22:36 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 22:36 Georgy Yakovlev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-29 21:49 [gentoo-commits] repo/gentoo:master commit in: app-editors/gedit-plugins/ Mart Raudsepp
2023-08-08 15:04 Matt Turner
2023-07-08  3:23 Matt Turner
2023-01-23  3:58 Matt Turner
2023-01-05 16:30 Matt Turner
2022-11-04 18:00 Matt Turner
2022-10-29 22:33 Matt Turner
2022-05-31 23:57 Sam James
2022-05-27 10:22 Pacho Ramos
2022-04-05  2:09 Matt Turner
2022-02-19 20:13 Matt Turner
2022-01-13  2:00 Georgy Yakovlev
2021-10-17 21:07 Mart Raudsepp
2021-04-29  2:09 Matt Turner
2021-04-12 21:59 Matt Turner
2021-04-12 21:59 Matt Turner
2021-01-05 18:30 Matt Turner
2021-01-05 18:30 Matt Turner
2021-01-03 17:05 Matt Turner
2020-08-16 21:02 Mart Raudsepp
2020-04-20 20:30 Mart Raudsepp
2020-03-22 11:47 Mart Raudsepp
2020-01-28  9:39 Mart Raudsepp
2019-12-22 20:47 Mart Raudsepp
2019-12-22 20:47 Mart Raudsepp
2019-12-04 20:17 Matt Turner
2019-05-26 18:50 Sobhan Mohammadpour
2019-05-18 13:41 Mart Raudsepp
2019-03-13 23:22 Mart Raudsepp
2018-10-31 11:47 Mart Raudsepp
2018-10-15 22:02 Remi Cardona
2018-05-01 16:22 Mikle Kolyada
2018-02-28 22:22 Michał Górny
2017-12-09 19:40 Pacho Ramos
2017-04-17 16:49 David Seifert
2017-03-16 19:13 David Seifert
2016-11-01 17:31 Gilles Dartiguelongue
2016-11-01 17:31 Gilles Dartiguelongue
2016-06-28  3:47 Alexandre Rostovtsev
2015-11-14 15:27 Pacho Ramos
2015-11-14 15:27 Pacho Ramos
2015-09-07 16:24 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=1641335573.bbb121d03b7987f20923ed7e8f9d6ed868d5aa6a.gyakovlev@gentoo \
    --to=gyakovlev@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