public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/kramdown/
Date: Tue, 28 Mar 2023 16:27:05 +0000 (UTC)	[thread overview]
Message-ID: <1680020799.29e50639cc7ef855e7fab73fa4e0f318560fd17c.sam@gentoo> (raw)

commit:     29e50639cc7ef855e7fab73fa4e0f318560fd17c
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Mar 28 16:26:39 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Mar 28 16:26:39 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=29e50639

dev-ruby/kramdown: Stabilize 2.4.0-r1 arm64, #903283

Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-ruby/kramdown/kramdown-2.4.0-r1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-ruby/kramdown/kramdown-2.4.0-r1.ebuild b/dev-ruby/kramdown/kramdown-2.4.0-r1.ebuild
index 42f06d05ddb1..ba30cdc1662c 100644
--- a/dev-ruby/kramdown/kramdown-2.4.0-r1.ebuild
+++ b/dev-ruby/kramdown/kramdown-2.4.0-r1.ebuild
@@ -16,7 +16,7 @@ HOMEPAGE="https://kramdown.gettalong.org/"
 LICENSE="MIT"
 
 SLOT="$(ver_cut 1)"
-KEYWORDS="amd64 arm ~arm64 ~hppa ppc ppc64 ~riscv ~s390 sparc x86"
+KEYWORDS="amd64 arm arm64 ~hppa ppc ppc64 ~riscv ~s390 sparc x86"
 IUSE="latex unicode"
 
 LATEX_DEPS="latex? ( dev-texlive/texlive-latex dev-texlive/texlive-latexextra )"


             reply	other threads:[~2023-03-28 16:27 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-28 16:27 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-12  7:42 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/kramdown/ Hans de Graaff
2023-04-02  1:51 Sam James
2023-03-29 13:04 Sam James
2023-03-28 16:25 Sam James
2023-03-28 15:05 Sam James
2023-03-28 15:03 Sam James
2023-03-28 14:59 Sam James
2023-03-28 14:59 Sam James
2023-03-28 14:59 Sam James
2023-03-28  9:41 Hans de Graaff
2023-03-18  0:02 Sam James
2023-03-06  6:51 Hans de Graaff
2022-09-10  5:47 Hans de Graaff
2022-07-04  5:21 Hans de Graaff
2022-07-03 10:48 Agostino Sarubbo
2022-05-02  6:02 Hans de Graaff
2022-04-26 14:38 Sam James
2022-04-04  5:41 Hans de Graaff
2022-02-28  7:06 Yixun Lan
2022-02-10 10:20 Sam James
2021-12-24 23:55 Sam James
2021-12-18  2:10 Sam James
2021-11-10 12:49 Jakov Smolić
2021-08-29 18:30 Sam James
2021-08-27 10:29 Marek Szuba
2021-03-20  7:39 Hans de Graaff
2021-03-20  7:39 Hans de Graaff
2021-03-08  7:18 Hans de Graaff
2020-07-20  8:30 Hans de Graaff
2020-06-29 17:26 Hans de Graaff
2020-05-03  8:33 Hans de Graaff
2020-04-26  5:28 Hans de Graaff
2020-03-14 15:21 Hans de Graaff
2020-03-09  7:06 Hans de Graaff
2019-05-08 19:59 Hans de Graaff
2019-04-13  6:34 Hans de Graaff
2018-12-12 15:00 Hans de Graaff
2018-12-10  7:47 Hans de Graaff
2018-12-10  7:33 Hans de Graaff
2018-05-21  5:16 Hans de Graaff
2018-04-30 20:11 Hans de Graaff
2018-04-16  5:16 Hans de Graaff
2018-03-27 21:38 Aaron Bauman
2017-12-09  7:55 Hans de Graaff
2017-08-26  8:27 Hans de Graaff
2017-06-29  5:19 Hans de Graaff
2017-04-20  5:30 Hans de Graaff
2017-02-27 14:19 Michael Weber
2017-01-22  2:21 Manuel Rüger
2017-01-11  6:48 Hans de Graaff
2016-12-29 13:06 Hans de Graaff
2016-12-09 12:44 Hans de Graaff
2016-11-29  7:41 Hans de Graaff
2016-08-19  6:00 Hans de Graaff
2016-05-28  8:41 Hans de Graaff
2016-05-01 22:44 Manuel Rüger
2016-03-21 22:11 Manuel Rüger
2016-03-06 19:12 Manuel Rüger
2016-03-02 21:33 Manuel Rüger
2016-02-18  6:47 Hans de Graaff
2015-10-27  5:47 Hans de Graaff
2015-10-10  6:33 Jeroen Roovers
2015-08-30  6:29 Hans de Graaff

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=1680020799.29e50639cc7ef855e7fab73fa4e0f318560fd17c.sam@gentoo \
    --to=sam@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