From: Alexander Turenko <alexander.turenko@tarantool.org> To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> Cc: tarantool-patches@freelists.org Subject: [tarantool-patches] Re: [PATCH v2 3/5] Merge box_error, stat and collations into core library Date: Fri, 4 May 2018 14:36:56 +0300 [thread overview] Message-ID: <20180504113656.s7ctowewwzrvfg7x@tkn_work_nb> (raw) In-Reply-To: <25b2b52bc741e5c6587a144e000860ef900edab2.1524955403.git.v.shpilevoy@tarantool.org> Vlad, One comment is below. WBR, Alexander Turenko. On Sun, Apr 29, 2018 at 01:45:11AM +0300, Vladislav Shpilevoy wrote: > The goal is to expose collations into Lua with no dependencies on > box library. But collations merge into core requires box_error > and stat libraries too. > diff --git a/src/box/lua/call.c b/src/box/lua/call.c > index be13812aa..b60c6c397 100644 > --- a/src/box/lua/call.c > +++ b/src/box/lua/call.c > @@ -30,7 +30,7 @@ > */ > #include "box/lua/call.h" > #include "box/call.h" > -#include "box/error.h" > +#include <error.h> > #include "fiber.h" > > #include "lua/utils.h" > diff --git a/src/box/lua/error.cc b/src/box/lua/error.cc > index 314907421..960ea2aa9 100644 > --- a/src/box/lua/error.cc > +++ b/src/box/lua/error.cc > @@ -40,7 +40,7 @@ extern "C" { > #include <errinj.h> > > #include "lua/utils.h" > -#include "box/error.h" > +#include "src/error.h" > > static int > luaT_error_raise(lua_State *L) Don't know what policy is in use in Tarantool. The diff above shows two different approaches to include the same header within the one commit. It seems that we don't use relative includes (with ..) and prefer either <> or "src/..." w/o any particular system. Right?
next prev parent reply other threads:[~2018-05-04 11:36 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-28 22:45 [tarantool-patches] [PATCH v2 0/5] Expose ICU into Lua Vladislav Shpilevoy 2018-04-28 22:45 ` [tarantool-patches] [PATCH v2 1/5] alter: fix assertion in collations alter Vladislav Shpilevoy 2018-04-28 22:45 ` [tarantool-patches] [PATCH v2 2/5] Move struct on_access_denied_ctx into error.h Vladislav Shpilevoy 2018-05-04 11:06 ` [tarantool-patches] " Alexander Turenko 2018-05-04 12:05 ` Vladislav Shpilevoy 2018-04-28 22:45 ` [tarantool-patches] [PATCH v2 3/5] Merge box_error, stat and collations into core library Vladislav Shpilevoy 2018-05-04 11:36 ` Alexander Turenko [this message] 2018-05-04 12:05 ` [tarantool-patches] " Vladislav Shpilevoy 2018-05-08 13:18 ` Konstantin Osipov 2018-05-10 21:06 ` Vladislav Shpilevoy 2018-04-28 22:45 ` [tarantool-patches] [PATCH v2 4/5] Always store built-in collations in the cache Vladislav Shpilevoy 2018-05-08 13:20 ` [tarantool-patches] " Konstantin Osipov 2018-04-28 22:45 ` [tarantool-patches] [PATCH v2 5/5] lua: introduce utf8 built-in globaly visible module Vladislav Shpilevoy 2018-05-04 22:33 ` [tarantool-patches] " Alexander Turenko 2018-05-04 23:32 ` Vladislav Shpilevoy 2018-05-05 0:18 ` Alexander Turenko 2018-05-05 0:24 ` Vladislav Shpilevoy 2018-05-05 0:38 ` Alexander Turenko 2018-05-05 0:45 ` Vladislav Shpilevoy 2018-05-08 13:21 ` Konstantin Osipov 2018-05-05 0:19 ` [tarantool-patches] Re: [PATCH v2 0/5] Expose ICU into Lua Alexander Turenko
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=20180504113656.s7ctowewwzrvfg7x@tkn_work_nb \ --to=alexander.turenko@tarantool.org \ --cc=tarantool-patches@freelists.org \ --cc=v.shpilevoy@tarantool.org \ --subject='[tarantool-patches] Re: [PATCH v2 3/5] Merge box_error, stat and collations into core library' \ /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