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-lang/luajit/
Date: Tue, 16 Jul 2024 22:46:42 +0000 (UTC)	[thread overview]
Message-ID: <1721169982.62dff9a75566d212ca41ea0cd4ddee12c5d858b4.sam@gentoo> (raw)

commit:     62dff9a75566d212ca41ea0cd4ddee12c5d858b4
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Jul 16 22:46:22 2024 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Jul 16 22:46:22 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=62dff9a7

dev-lang/luajit: Stabilize 2.1.1716656478 arm, #936162

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

 dev-lang/luajit/luajit-2.1.1716656478.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-lang/luajit/luajit-2.1.1716656478.ebuild b/dev-lang/luajit/luajit-2.1.1716656478.ebuild
index a4275091a81f..c6005e5ba970 100644
--- a/dev-lang/luajit/luajit-2.1.1716656478.ebuild
+++ b/dev-lang/luajit/luajit-2.1.1716656478.ebuild
@@ -23,7 +23,7 @@ S="${WORKDIR}/LuaJIT-${GIT_COMMIT}"
 LICENSE="MIT"
 # this should probably be pkgmoved to 2.0 for sake of consistency.
 SLOT="2/${PV}"
-KEYWORDS="amd64 ~arm ~arm64 -hppa ~mips ~ppc -riscv -sparc x86 ~amd64-linux ~x86-linux"
+KEYWORDS="amd64 arm ~arm64 -hppa ~mips ~ppc -riscv -sparc x86 ~amd64-linux ~x86-linux"
 IUSE="lua52compat static-libs"
 
 _emake() {


             reply	other threads:[~2024-07-16 22:46 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-16 22:46 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-10  2:37 [gentoo-commits] repo/gentoo:master commit in: dev-lang/luajit/ Matt Turner
2024-09-10  2:37 Matt Turner
2024-07-16 22:46 Sam James
2024-07-16 22:46 Sam James
2024-07-16 19:18 Arthur Zamarin
2024-07-16 19:18 Arthur Zamarin
2024-07-16 17:46 William Hubbs
2024-06-09  3:38 Matt Turner
2023-11-13 22:15 James Le Cuirot
2023-09-10 12:25 Sam James
2023-03-19 17:36 Arthur Zamarin
2022-12-06  9:25 Sam James
2022-06-20 17:16 William Hubbs
2022-06-20 16:56 William Hubbs
2022-06-20 16:23 William Hubbs
2022-06-18 16:55 Agostino Sarubbo
2022-06-17 11:37 Agostino Sarubbo
2022-06-17 10:29 Jakov Smolić
2022-06-17 10:29 Jakov Smolić
2022-06-17  6:56 Agostino Sarubbo
2022-04-19 23:58 Sam James
2022-02-15 23:30 William Hubbs
2022-02-15  4:22 William Hubbs
2021-06-25 12:32 Marek Szuba
2021-03-07 18:46 Sergei Trofimovich
2020-12-14  1:20 William Hubbs
2020-12-14  1:20 William Hubbs
2020-12-08 12:42 Thomas Deutschmann
2020-12-08 12:42 Thomas Deutschmann
2020-12-08 12:42 Thomas Deutschmann
2020-12-07 18:46 William Hubbs
2020-12-07 18:46 William Hubbs
2020-12-07 18:28 William Hubbs
2020-10-24 11:49 Rafael Martins
2020-07-25 15:14 Rafael Martins
2020-07-25 11:16 Sam James
2020-07-23 23:45 Sam James
2020-07-23 21:52 Sam James
2020-07-23 20:36 Sam James
2020-02-01 21:46 Rafael Martins
2019-03-22 19:42 Rafael Martins
2018-07-08 10:48 Markus Meier
2018-06-26  2:04 Aaron Bauman
2018-05-26 20:31 Aaron Bauman
2018-03-26  6:21 Michał Górny
2018-03-22 14:24 Guilherme Amadio
2018-03-14  2:07 Rafael Martins
2016-01-14 21:57 Markus Meier
2016-01-05 10:49 Agostino Sarubbo

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=1721169982.62dff9a75566d212ca41ea0cd4ddee12c5d858b4.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