From: "Markus Meier" <maekke@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-lang/luajit/
Date: Thu, 14 Jan 2016 21:57:41 +0000 (UTC) [thread overview]
Message-ID: <1452808644.2973ad531f33e8fb622c71fd87802416f1371d60.maekke@gentoo> (raw)
commit: 2973ad531f33e8fb622c71fd87802416f1371d60
Author: Markus Meier <maekke <AT> gentoo <DOT> org>
AuthorDate: Thu Jan 14 21:57:24 2016 +0000
Commit: Markus Meier <maekke <AT> gentoo <DOT> org>
CommitDate: Thu Jan 14 21:57:24 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2973ad53
dev-lang/luajit: arm stable, bug #570808
Package-Manager: portage-2.2.26
RepoMan-Options: --include-arches="arm"
dev-lang/luajit/luajit-2.0.4.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-lang/luajit/luajit-2.0.4.ebuild b/dev-lang/luajit/luajit-2.0.4.ebuild
index 0c2d1d3..ed95424 100644
--- a/dev-lang/luajit/luajit-2.0.4.ebuild
+++ b/dev-lang/luajit/luajit-2.0.4.ebuild
@@ -21,7 +21,7 @@ SRC_URI="http://luajit.org/download/${MY_P}.tar.gz
LICENSE="MIT"
# this should probably be pkgmoved to 2.0 for sake of consistency.
SLOT="2"
-KEYWORDS="amd64 ~arm ~ppc x86 ~amd64-linux ~x86-linux"
+KEYWORDS="amd64 arm ~ppc x86 ~amd64-linux ~x86-linux"
IUSE="lua52compat"
S="${WORKDIR}/${MY_P}"
next reply other threads:[~2016-01-14 21:57 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 21:57 Markus Meier [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-26 1:37 [gentoo-commits] repo/gentoo:master commit in: dev-lang/luajit/ Sam James
2025-04-26 1:26 Sam James
2025-04-26 0:32 Sam James
2025-04-26 0:32 Sam James
2024-11-24 14:59 Joonas Niilola
2024-11-21 9:24 Sam James
2024-11-14 3:23 Sam James
2024-11-13 5:10 Sam James
2024-11-13 5:10 Sam James
2024-11-12 21:47 Sam James
2024-09-10 2:37 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 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-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=1452808644.2973ad531f33e8fb622c71fd87802416f1371d60.maekke@gentoo \
--to=maekke@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