public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/markdown2/
Date: Tue, 12 May 2020 06:39:17 +0000 (UTC)	[thread overview]
Message-ID: <1589265496.fec6b5567cfd97d888c1112cd64778556d3f87e9.ago@gentoo> (raw)

commit:     fec6b5567cfd97d888c1112cd64778556d3f87e9
Author:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Tue May 12 06:38:16 2020 +0000
Commit:     Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Tue May 12 06:38:16 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fec6b556

dev-python/markdown2: x86 stable wrt bug #722226

Package-Manager: Portage-2.3.99, Repoman-2.3.22
RepoMan-Options: --include-arches="x86"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>

 dev-python/markdown2/markdown2-2.3.8.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/markdown2/markdown2-2.3.8.ebuild b/dev-python/markdown2/markdown2-2.3.8.ebuild
index d513cf879f5..34140e887c9 100644
--- a/dev-python/markdown2/markdown2-2.3.8.ebuild
+++ b/dev-python/markdown2/markdown2-2.3.8.ebuild
@@ -13,7 +13,7 @@ HOMEPAGE="https://github.com/trentm/python-markdown2"
 
 LICENSE="MIT"
 SLOT="0"
-KEYWORDS="amd64 ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS="amd64 x86 ~amd64-linux ~x86-linux"
 
 RDEPEND="dev-python/pygments[${PYTHON_USEDEP}]"
 


             reply	other threads:[~2020-05-12  6:39 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12  6:39 Agostino Sarubbo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-26 13:13 [gentoo-commits] repo/gentoo:master commit in: dev-python/markdown2/ Michał Górny
2024-10-26 13:10 Michał Górny
2024-10-10  5:03 Michał Górny
2024-07-27  7:19 Michał Górny
2024-07-27  7:01 Arthur Zamarin
2024-07-12  2:33 Michał Górny
2024-06-29 14:47 Arthur Zamarin
2024-06-15 15:08 Petr Vaněk
2024-03-13 15:02 Michał Górny
2024-03-13 14:05 Arthur Zamarin
2024-02-26  4:35 Michał Górny
2024-01-06  9:54 Michał Górny
2024-01-06  9:50 Michał Górny
2023-12-20 15:51 Michał Górny
2023-12-20 15:47 Michał Górny
2023-12-18  5:18 Michał Górny
2023-12-04  6:48 Michał Górny
2023-11-24 16:26 Michał Górny
2023-09-25 18:49 Michał Górny
2023-09-25 17:04 Arthur Zamarin
2023-09-12 15:25 Arthur Zamarin
2023-08-25  3:58 Jakov Smolić
2023-08-24 13:46 Sam James
2023-07-25  5:20 Michał Górny
2023-07-24 10:52 Michał Górny
2023-07-24  8:54 Jakov Smolić
2023-06-23  5:35 Michał Górny
2023-06-07  9:27 Sam James
2023-02-23  6:19 Michał Górny
2023-02-22 20:30 Arthur Zamarin
2023-02-13  6:05 Michał Górny
2023-01-23  7:34 Michał Górny
2022-11-03 19:48 Arthur Zamarin
2022-11-03 19:47 Arthur Zamarin
2022-10-21  5:14 Michał Górny
2022-09-26 10:30 Michał Górny
2022-06-22  7:42 Michał Górny
2022-06-22  5:47 Agostino Sarubbo
2022-05-29 19:16 Arthur Zamarin
2022-04-28  8:31 Michał Górny
2021-12-02 19:58 Michał Górny
2021-12-02 19:48 Sam James
2021-12-02  8:12 Michał Górny
2021-09-18 19:43 Michał Górny
2021-09-18 17:29 Sam James
2021-08-18  6:56 Michał Górny
2021-06-05 14:30 Michał Górny
2021-01-24 21:48 Michał Górny
2021-01-24 20:06 Sam James
2021-01-23  0:54 Michał Górny
2020-12-13 12:15 Michał Górny
2020-12-13  8:58 Sam James
2020-12-11 23:12 Sergei Trofimovich
2020-12-11 23:07 Sergei Trofimovich
2020-12-05  9:52 Michał Górny
2020-10-31  1:05 Louis Sautier
2020-10-20  2:50 Michał Górny
2020-09-20 12:58 Sam James
2020-09-20 12:49 Michał Górny
2020-07-14 16:58 Sergei Trofimovich
2020-07-05  8:38 Sergei Trofimovich
2020-06-20  0:48 Aaron Bauman
2020-06-07  8:48 Agostino Sarubbo
2020-06-07  8:44 Agostino Sarubbo
2020-05-13  7:08 Michał Górny
2020-05-11 11:28 Agostino Sarubbo
2020-04-21  9:16 Michał Górny
2020-02-05 16:24 Michał Górny
2017-05-02 15:15 Michał Górny
2017-04-26 15:26 Michał Górny
2016-03-18 19:11 Michał Górny

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=1589265496.fec6b5567cfd97d888c1112cd64778556d3f87e9.ago@gentoo \
    --to=ago@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