From: Jason at zx2c4.com (Jason A. Donenfeld)
Subject: lua vs luajit vs both
Date: Tue, 14 Jan 2014 02:02:40 +0100 [thread overview]
Message-ID: <CAHmME9pMcrZ=sJ=u-2fSONef+4beNEogf2vYzbfH3AuRLMFgAw@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9r7=4eQ6BFnPu8eD8Qb3Ut-L1mg2CvP49_Phb38zuN-8A@mail.gmail.com>
I've gone ahead and merged the lua work to master, for testing and
subsequent cleanup before release.
Regarding "to jit or not to jit", I currently have this fancy autodetection
logic:
http://git.zx2c4.com/cgit/commit/?id=3488d124052f5c3ddef303ed5306ad6a458794c1
John -- I'm waiting for your input on the parent email, as you seem to be
the originator of the opinion that "both are good".
Please -- everybody -- test master and let me know any regressions.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20140114/0290e74d/attachment.html>
next prev parent reply other threads:[~2014-01-14 1:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 16:03 Jason
2014-01-14 1:02 ` Jason [this message]
2014-01-14 9:08 ` john
2014-01-14 18:06 ` Jason
2014-01-14 22:54 ` john
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='CAHmME9pMcrZ=sJ=u-2fSONef+4beNEogf2vYzbfH3AuRLMFgAw@mail.gmail.com' \
--to=cgit@lists.zx2c4.com \
/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).