Tarantool development patches archive
 help / color / mirror / Atom feed
From: Konstantin Osipov <kostja.osipov@gmail.com>
To: Olga Arkhangelskaia <arkholga@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH v5] build: introduce LUAJIT_ENABLE_PAIRSMM flag
Date: Tue, 26 Nov 2019 23:54:27 +0300	[thread overview]
Message-ID: <20191126205427.GB23422@atlas> (raw)
In-Reply-To: <20191126144837.78132-1-arkholga@tarantool.org>

* Olga Arkhangelskaia <arkholga@tarantool.org> [19/11/26 17:52]:
> Adds LUAJIT_ENABLE_PAIRSMM flag as a build option for luajit.
> If the flag is set, pairs/ipairs metamethods are available in Lua 5.1.
> For tarantool this option is enabled by default.
> 
> Part of #4560
> Branch:https://github.com/tarantool/luajit/tree/OKriw/gh-4560-Enable-LUAJIT_ENABLE_LUA52COMPAT-when-bulding-luajit
> 
> v1: https://lists.tarantool.org/pipermail/tarantool-patches/2019-November/012466.html
> v2: https://lists.tarantool.org/pipermail/tarantool-patches/2019-November/012489.html
> v3: https://lists.tarantool.org/pipermail/tarantool-patches/2019-November/012527.html
> 
> Changes in v2:
> - flag is renamed
> - now flag is used only for pairsmm
> - added test case
> Changes in v3:
> - added flag to other vm*
> - changed comments and commit msg
> Changes in v4:
> - fixed errors in arm/arm64 vm
> - rewrited commit msg, subject, comment 
> 
> Changes in v5:
> - fixed test name

It's nice there are so many changes, but usually they are from
newest to oldest, not from oldest to newest.


-- 
Konstantin Osipov, Moscow, Russia

  parent reply	other threads:[~2019-11-26 20:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-26 14:48 Olga Arkhangelskaia
2019-11-26 14:55 ` Cyrill Gorcunov
2019-11-26 15:14 ` Igor Munkin
2019-11-26 20:54 ` Konstantin Osipov [this message]
2020-02-19  7:49 ` Kirill Yukhin

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=20191126205427.GB23422@atlas \
    --to=kostja.osipov@gmail.com \
    --cc=arkholga@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH v5] build: introduce LUAJIT_ENABLE_PAIRSMM flag' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox