I forgot to link to the releases.
- luvi v2.3.2 - https://github.com/luvit/luvi/releases/tag/v2.3.2
- lit v2.2.9 - https://github.com/luvit/lit/releases/tag/2.2.9
- luvit v2.5.2 - https://github.com/luvit/luvit/releases/tag/2.5.2
Also while `lit update` should do the minimal work to bring your system up
to date, it doesn't hurt to force a rebuild of lit and luvit afterwards by
running:
lit make lit://luvit/lit `which lit`
lit make lit://luvit/luvit `which luvit`
Depending on how old your lit version is, it might not build the new binary
correctly, forcing a rebuild this way after running `lit update` will fix
this.
-Tim Caswell
On Wed, Aug 26, 2015 at 1:29 PM, Tim Caswell <[email protected]> wrote:
> I just released new luvi/lit/luvit versions to github and lit.
>
> * Show all luvi option versions in `luvit -v` [Ryan Phillips]
> * libuv: Update libuv to v1.7.2 [Tim Caswell]
> * luv: Performance tweaks and memory leak fixes for threads [George Zhao]
> * luvi: Add proper thread linking for luajit [Ryan Phillips]
> * lit: Fix auth on windows when git isn't installed [Tim Caswell]
>
> This release is mostly bug fixes across the board. Updating is
> recommended using `lit update`.
>
> -Tim Caswell
>
--
You received this message because you are subscribed to the Google Groups
"luvit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
