public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Anthony G. Basile" <blueness@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/sphinxcontrib-blockdiag/
Date: Sat, 16 Mar 2019 23:17:40 +0000 (UTC)	[thread overview]
Message-ID: <1552778253.f32fad01aae47270ade31d3292fbddf162458b21.blueness@gentoo> (raw)

commit:     f32fad01aae47270ade31d3292fbddf162458b21
Author:     Anthony G. Basile <blueness <AT> gentoo <DOT> org>
AuthorDate: Sat Mar 16 23:17:08 2019 +0000
Commit:     Anthony G. Basile <blueness <AT> gentoo <DOT> org>
CommitDate: Sat Mar 16 23:17:33 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f32fad01

dev-python/sphinxcontrib-blockdiag: keyword ~arm

Signed-off-by: Anthony G. Basile <blueness <AT> gentoo.org>
Package-Manager: Portage-2.3.51, Repoman-2.3.11

 .../sphinxcontrib-blockdiag/sphinxcontrib-blockdiag-1.5.5-r1.ebuild   | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/dev-python/sphinxcontrib-blockdiag/sphinxcontrib-blockdiag-1.5.5-r1.ebuild b/dev-python/sphinxcontrib-blockdiag/sphinxcontrib-blockdiag-1.5.5-r1.ebuild
index 775f0da1e16..129b1d3bd82 100644
--- a/dev-python/sphinxcontrib-blockdiag/sphinxcontrib-blockdiag-1.5.5-r1.ebuild
+++ b/dev-python/sphinxcontrib-blockdiag/sphinxcontrib-blockdiag-1.5.5-r1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2017 Gentoo Foundation
+# Copyright 1999-2019 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=6
@@ -16,7 +16,7 @@ LICENSE="BSD"
 
 SLOT="0"
 
-KEYWORDS="~amd64 ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS="~amd64 ~arm ~x86 ~amd64-linux ~x86-linux"
 
 IUSE=""
 


             reply	other threads:[~2019-03-16 23:17 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-16 23:17 Anthony G. Basile [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-07-10 18:50 [gentoo-commits] repo/gentoo:master commit in: dev-python/sphinxcontrib-blockdiag/ Michał Górny
2022-07-10 16:56 Sam James
2022-06-05 18:22 Michał Górny
2022-04-26 20:28 Michał Górny
2022-04-26 19:11 Arthur Zamarin
2022-04-26 17:01 Michał Górny
2022-04-26  3:07 Sam James
2022-04-20 12:18 Michał Górny
2021-07-27 23:11 Marek Szuba
2021-06-22 21:28 Michał Górny
2021-03-28 22:16 Brian Dolbec
2020-12-04 12:38 Michał Górny
2020-12-03 17:31 Michał Górny
2020-11-26 19:08 Sam James
2020-11-26 13:21 Sam James
2020-10-07  1:02 Sam James
2020-10-04 19:49 Sergei Trofimovich
2020-10-01 17:29 Sergei Trofimovich
2020-09-30 20:26 Sam James
2020-09-27  6:42 Matt Turner
2020-09-13  4:55 Sam James
2020-09-13  3:31 Sam James
2020-08-25 10:23 Sam James
2020-08-18 21:53 Sergei Trofimovich
2020-03-29  9:16 Michał Górny
2020-02-05 13:24 Michał Górny
2019-12-30 21:54 Piotr Karbowski
2019-12-09  8:39 Michał Górny
2019-07-31 14:32 Mikle Kolyada
2019-07-29 10:48 Mikle Kolyada
2019-07-22 14:12 Aaron Bauman
2019-07-14 12:27 Michał Górny
2019-07-14 12:27 Michał Górny
2019-07-14 12:27 Michał Górny
2019-04-27 11:49 Anthony G. Basile
2017-10-08 11:00 Michał Górny
2017-08-02  4:06 Sebastien Fabbro
2017-06-02 17:31 David Seifert
2017-05-16  2:10 Brian Dolbec
2017-04-07 14:14 Michał Górny
2017-02-10 21:52 Brian Dolbec

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=1552778253.f32fad01aae47270ade31d3292fbddf162458b21.blueness@gentoo \
    --to=blueness@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