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: dev-python/sphinxcontrib-programoutput/
Date: Sun, 24 Jun 2018 09:40:03 +0000 (UTC)	[thread overview]
Message-ID: <1529833196.7a49ee5811d209f5b33f594dc349f6c458eefe10.zlogene@gentoo> (raw)

commit:     7a49ee5811d209f5b33f594dc349f6c458eefe10
Author:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Sun Jun 24 09:37:35 2018 +0000
Commit:     Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Sun Jun 24 09:39:56 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7a49ee58

dev-python/sphinxcontrib-programoutput: amd64 stable wrt bug #658884

Package-Manager: Portage-2.3.40, Repoman-2.3.9

 .../sphinxcontrib-programoutput/sphinxcontrib-programoutput-0.11.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/sphinxcontrib-programoutput/sphinxcontrib-programoutput-0.11.ebuild b/dev-python/sphinxcontrib-programoutput/sphinxcontrib-programoutput-0.11.ebuild
index 26c570b6344..3a96759fffa 100644
--- a/dev-python/sphinxcontrib-programoutput/sphinxcontrib-programoutput-0.11.ebuild
+++ b/dev-python/sphinxcontrib-programoutput/sphinxcontrib-programoutput-0.11.ebuild
@@ -13,7 +13,7 @@ SRC_URI="mirror://pypi/${PN:0:1}/${PN}/${P}.tar.gz"
 
 LICENSE="BSD"
 SLOT="0"
-KEYWORDS="~amd64 ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS="amd64 ~x86 ~amd64-linux ~x86-linux"
 
 IUSE="doc test"
 


             reply	other threads:[~2018-06-24  9:40 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-24  9:40 Mikle Kolyada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-28 10:47 [gentoo-commits] repo/gentoo:master commit in: dev-python/sphinxcontrib-programoutput/ Michał Górny
2024-12-08 17:34 Arthur Zamarin
2024-12-07 11:59 Michał Górny
2024-12-07  7:07 Michał Górny
2023-05-30 16:01 Sam James
2023-03-17 15:25 Michał Górny
2023-02-13  3:22 Matt Turner
2023-01-24 20:24 Arthur Zamarin
2022-05-11 12:56 Jakov Smolić
2022-04-26 20:28 Michał Górny
2022-04-26 19:21 Arthur Zamarin
2022-04-20 12:18 Michał Górny
2022-02-07 22:29 Sam James
2022-02-07 20:14 Arthur Zamarin
2022-02-07  9:35 Sam James
2021-11-19 11:39 Arthur Zamarin
2021-11-19  7:59 Arthur Zamarin
2021-11-18 10:50 Sam James
2021-11-15 16:29 Agostino Sarubbo
2021-10-09  8:29 Arthur Zamarin
2021-09-10  1:27 Sam James
2021-07-12  0:58 Sam James
2021-07-08  7:11 Sergei Trofimovich
2021-07-08  7:09 Sergei Trofimovich
2021-06-24 15:07 Sergei Trofimovich
2021-05-07 13:44 Michał Górny
2021-05-07 13:28 Sam James
2021-04-01  7:43 Michał Górny
2020-12-04 12:38 Michał Górny
2020-12-03 17:31 Michał Górny
2020-08-05 15:18 Michał Górny
2020-07-29 10:20 Michał Górny
2020-06-15 10:57 Joonas Niilola
2020-06-15 10:57 Joonas Niilola
2020-05-21  8:06 Agostino Sarubbo
2020-05-21  7:53 Agostino Sarubbo
2020-03-18  8:30 Joonas Niilola
2020-03-17  7:48 Joonas Niilola
2020-01-18 18:48 Michał Górny
2019-12-29  8:53 David Seifert
2018-07-21  0:06 Mikle Kolyada
2018-04-29  6:33 Michał Górny
2017-08-02  4:06 Sebastien Fabbro
2015-12-03 14:35 Justin Lecher

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=1529833196.7a49ee5811d209f5b33f594dc349f6c458eefe10.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