From: CameronNemo <CameronNemo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: LuaJIT: update to git v2.1 branch
Date: Fri, 27 May 2022 22:04:46 +0200 [thread overview]
Message-ID: <20220527200446.OelJIwmJoDmmA_J5qmxRRFqu-aREH0TGpZGYKWDuJuU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36790@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]
There's a closed pull request on the void-packages repository
LuaJIT: update to git v2.1 branch
https://github.com/void-linux/void-packages/pull/36790
Description:
CC: @q66
The LuaJIT maintainer has not published a new version in 5 years, but he
has steadily added commits to the "2.1" branch, linked below.
https://repo.or.cz/luajit-2.0.git/shortlog/refs/heads/v2.1
Projects like neovim build against this branch or master due to the lack
of a recent release.
Furthermore, distributions such as Arch Linux and Debian Sid are
building from a commit rather than a release.
https://github.com/archlinux/svntogit-community/commit/11473c3c786593b2438a865519d407c7a84ce0a1
https://salsa.debian.org/lua-team/luajit/-/commit/e06cbc6d2a61b253056214f5ed3f03ce661e31f9
The LuaJIT upstream maintainer has declined to cut a release, reasoning
"Releases are an antiquated concept".
https://github.com/LuaJIT/LuaJIT/issues/665#issuecomment-784452583
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**, on x86_64 and aarch64
prev parent reply other threads:[~2022-05-27 20:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 0:48 [PR PATCH] " CameronNemo
2022-04-21 4:04 ` q66
2022-04-21 4:06 ` q66
2022-04-21 4:08 ` q66
2022-04-21 4:13 ` CameronNemo
2022-04-21 4:15 ` CameronNemo
2022-04-21 11:53 ` mhmdanas
2022-04-21 16:02 ` gbrlsnchs
2022-04-22 11:43 ` Idesmi
2022-04-23 7:27 ` kartikynwa
2022-04-23 12:05 ` LinArcX
2022-04-23 12:44 ` q66
2022-04-23 12:54 ` Idesmi
2022-04-23 13:38 ` q66
2022-04-23 13:38 ` q66
2022-05-02 5:03 ` kartikynwa
2022-05-03 6:24 ` CameronNemo
2022-05-06 9:38 ` mitinarseny
2022-05-27 20:04 ` CameronNemo [this message]
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=20220527200446.OelJIwmJoDmmA_J5qmxRRFqu-aREH0TGpZGYKWDuJuU@z \
--to=cameronnemo@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).