public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/markdown-it-py/
Date: Sat, 22 Oct 2022 16:44:50 +0000 (UTC)	[thread overview]
Message-ID: <1666457079.05d5cd1c85ccfb17a2cb4253543e318c7164da68.arthurzam@gentoo> (raw)

commit:     05d5cd1c85ccfb17a2cb4253543e318c7164da68
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Sat Oct 22 16:44:39 2022 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Sat Oct 22 16:44:39 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=05d5cd1c

dev-python/markdown-it-py: Stabilize 2.1.0-r2 arm64, #877947

Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>

 dev-python/markdown-it-py/markdown-it-py-2.1.0-r2.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/markdown-it-py/markdown-it-py-2.1.0-r2.ebuild b/dev-python/markdown-it-py/markdown-it-py-2.1.0-r2.ebuild
index d99094c735d7..66c854b3477e 100644
--- a/dev-python/markdown-it-py/markdown-it-py-2.1.0-r2.ebuild
+++ b/dev-python/markdown-it-py/markdown-it-py-2.1.0-r2.ebuild
@@ -20,7 +20,7 @@ SRC_URI="
 
 LICENSE="MIT"
 SLOT="0"
-KEYWORDS="~alpha ~amd64 arm ~arm64 ~hppa ~ia64 ~m68k ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86"
+KEYWORDS="~alpha ~amd64 arm arm64 ~hppa ~ia64 ~m68k ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86"
 
 RDEPEND="
 	dev-python/linkify-it-py[${PYTHON_USEDEP}]


             reply	other threads:[~2022-10-22 16:44 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-22 16:44 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-11 11:05 [gentoo-commits] repo/gentoo:master commit in: dev-python/markdown-it-py/ Michał Górny
2023-07-05  8:14 Michał Górny
2023-07-05  8:01 Arthur Zamarin
2023-06-04  5:44 Michał Górny
2023-05-29 12:49 Michał Górny
2023-04-05  8:10 Michał Górny
2023-04-05  7:04 Arthur Zamarin
2023-03-19 17:36 Arthur Zamarin
2023-02-23  6:19 Michał Górny
2023-01-25 16:10 WANG Xuerui
2022-10-25 14:06 Michał Górny
2022-10-25 12:49 Sam James
2022-10-25 12:49 Sam James
2022-10-23  7:53 Agostino Sarubbo
2022-10-22 17:32 Arthur Zamarin
2022-10-22 16:49 Arthur Zamarin
2022-10-22 16:49 Arthur Zamarin
2022-10-22 16:44 Arthur Zamarin
2022-10-08 22:36 James Le Cuirot
2022-10-07  7:03 Michał Górny
2022-09-26  6:48 Arthur Zamarin
2022-09-26  6:47 Arthur Zamarin
2022-09-19 19:04 Arthur Zamarin
2022-09-19 17:08 Arthur Zamarin
2022-09-19 17:08 Arthur Zamarin
2022-09-19 17:08 Arthur Zamarin
2022-09-19  5:36 Yixun Lan
2022-09-18 20:30 Arthur Zamarin
2022-09-18 20:30 Arthur Zamarin
2022-09-18 20:30 Arthur Zamarin
2022-09-18 18:50 Michał Górny
2022-09-18  8:18 Michał Górny
2022-07-06 22:01 James Le Cuirot
2022-06-24 15:46 Michał Górny
2022-05-29 19:16 Arthur Zamarin
2022-05-21 19:22 Michał Górny
2022-05-21 17:35 Jakov Smolić
2022-04-16 15:36 Arthur Zamarin
2022-03-12 12:46 Arthur Zamarin
2022-03-12 12:46 Arthur Zamarin
2022-03-12 12:46 Arthur Zamarin
2022-03-12 12:01 Arthur Zamarin
2022-03-02  9:08 Agostino Sarubbo
2022-03-02  9:07 Agostino Sarubbo
2022-03-02  9:04 Agostino Sarubbo
2022-03-01 11:28 Agostino Sarubbo
2022-02-27 10:52 Michał Górny
2022-02-09 14:18 Yixun Lan
2022-02-08 17:38 Arthur Zamarin
2022-02-07 22:29 Sam James
2022-02-07 11:36 Sam James
2022-02-07 11:32 Sam James
2022-02-07 11:31 Sam James
2022-02-07 11:30 Sam James
2022-02-07 11:18 Sam James
2022-02-07  8:33 Sam James
2022-01-24 22:14 Michał Górny
2022-01-23 18:49 Arthur Zamarin

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=1666457079.05d5cd1c85ccfb17a2cb4253543e318c7164da68.arthurzam@gentoo \
    --to=arthurzam@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