public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: gnome-extra/chrome-gnome-shell/
Date: Sun, 18 Nov 2018 09:51:53 +0000 (UTC)	[thread overview]
Message-ID: <1542534626.94d09c42af38901d0a461a14462c18980d40f648.zlogene@gentoo> (raw)

commit:     94d09c42af38901d0a461a14462c18980d40f648
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Sun Nov 18 09:50:26 2018 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Sun Nov 18 09:50:26 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=94d09c42

gnome-extra/chrome-gnome-shell: Add ~arm keyword wrt bug #583422

Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>
Package-Manager: Portage-2.3.51, Repoman-2.3.11

 gnome-extra/chrome-gnome-shell/chrome-gnome-shell-10.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gnome-extra/chrome-gnome-shell/chrome-gnome-shell-10.ebuild b/gnome-extra/chrome-gnome-shell/chrome-gnome-shell-10.ebuild
index 3f8d388c296..2389b912cc2 100644
--- a/gnome-extra/chrome-gnome-shell/chrome-gnome-shell-10.ebuild
+++ b/gnome-extra/chrome-gnome-shell/chrome-gnome-shell-10.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2018 Gentoo Foundation
+# Copyright 1999-2018 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=6
@@ -13,7 +13,7 @@ SRC_URI="mirror://gnome/sources/${PN}/${PV}/${P}.tar.xz"
 
 LICENSE="GPL-3+"
 SLOT="0"
-KEYWORDS="~alpha amd64 ~ia64 ~ppc ~ppc64 x86"
+KEYWORDS="~alpha amd64 ~arm ~ia64 ~ppc ~ppc64 x86"
 IUSE=""
 
 REQUIRED_USE="${PYTHON_REQUIRED_USE}"


             reply	other threads:[~2018-11-18  9:51 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-18  9:51 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-03-13 17:26 [gentoo-commits] repo/gentoo:master commit in: gnome-extra/chrome-gnome-shell/ Sam James
2022-03-13 17:26 Sam James
2022-03-13 11:54 Jakov Smolić
2022-03-12 12:08 Jakov Smolić
2022-03-11 16:16 Sam James
2021-12-28  3:11 Georgy Yakovlev
2021-03-04  0:23 Sam James
2021-02-25 12:02 Ben Kohler
2021-01-01  0:59 Michał Górny
2020-04-25 21:14 Mart Raudsepp
2020-04-25 18:04 Matt Turner
2020-02-10 11:54 Michał Górny
2020-02-09 16:25 Michał Górny
2020-01-07 17:34 Ben Kohler
2020-01-07 17:26 Ben Kohler
2019-08-03 19:04 Aaron Bauman
2019-06-20  9:20 Mikle Kolyada
2019-04-19 12:52 Michał Górny
2018-10-16  9:18 Tobias Klausmann
2018-04-25 20:27 Thomas Deutschmann
2018-04-06 14:43 Aaron Bauman
2018-02-17 15:26 Patrice Clement
2018-02-17 15:26 Patrice Clement
2017-09-17 11:42 Sergei Trofimovich
2017-09-17 11:14 Sergei Trofimovich
2017-07-10  7:08 Sergei Trofimovich
2017-04-26 21:03 Patrice Clement
2017-04-26 21:03 Patrice Clement
2017-03-02 10:41 Agostino Sarubbo
2017-03-02 10:40 Agostino Sarubbo
2017-02-18  4:37 Michael Palimaka
2017-01-26  3:14 Mart Raudsepp
2017-01-25 11:03 Mikhail Pukhlikov
2017-01-18 10:18 David Seifert
2017-01-04 23:18 Patrice Clement
2016-09-26 11:25 Patrice Clement
2016-09-17 14:44 Patrice Clement
2016-08-07 20:43 Patrice Clement
2016-05-18  6:30 Ian Delaney

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=1542534626.94d09c42af38901d0a461a14462c18980d40f648.zlogene@gentoo \
    --to=zlogene@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