From: hippi777 <hippi777@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New Package: awesome-LuaJIT
Date: Sun, 29 Mar 2020 18:28:14 +0200 [thread overview]
Message-ID: <20200329162814.v5RTPpF2cvYoxVOJ4GupMrmLiMP0x_6DqpbXyCNYRtA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-16137@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 914 bytes --]
New comment by hippi777 on void-packages repository
https://github.com/void-linux/void-packages/pull/16137#issuecomment-605662648
Comment:
hi folks! :)
@q66, luajit is alive, there was no sign about Mike (its main developer) for something like a year, and he announced before that, that he has other duties, but some months ago he reappeared and started to work on luajit again. in the meantime, moonjit appeared, and its main purpose is to be a drop in replacement for luajit, and basically it collects the pending pull requests for luajit and makes releases more often. (< in case of interest...) however luajit is actually under development now, just no fresh release came out for a long while.
btw i dunno why its written formally, as LuaJIT, instead of luajit in the package name, but im a new kid here... :D
otherwise +1 for a build option instead, but ive got no interest in this...
bests! :)
next prev parent reply other threads:[~2020-03-29 16:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 4:35 [PR PATCH] Awesome luajit voidlinux-github
2019-11-10 11:00 ` New Package: awesome-LuaJIT voidlinux-github
2020-03-09 18:44 ` ndgnuh
2020-03-29 15:35 ` q66
2020-03-29 16:28 ` ndgnuh
2020-03-29 16:28 ` hippi777 [this message]
2020-03-29 16:30 ` ndgnuh
2020-03-29 17:53 ` ndgnuh
2020-03-29 17:53 ` ndgnuh
2020-03-29 20:46 ` q66
2020-03-29 20:46 ` [PR PATCH] [Closed]: " q66
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=20200329162814.v5RTPpF2cvYoxVOJ4GupMrmLiMP0x_6DqpbXyCNYRtA@z \
--to=hippi777@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).