From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> To: Leonid Vasiliev <lvasiliev@tarantool.org> Cc: Yaroslav Dynnikov <Yaroslav.dynnikov@tarantool.org>, tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH v2] rocks: forward options to luarocks Date: Fri, 10 Apr 2020 02:00:34 +0200 [thread overview] Message-ID: <cbdb690e-7368-08ad-1bc8-fb387f3a2bdb@tarantool.org> (raw) In-Reply-To: <2d94d49b51bd326d79a032cdfe0307480b2f5475.1586097801.git.lvasiliev@tarantool.org> Thanks for the patch! I added Yaroslav to CC since he expressed a will to join the review. On 05/04/2020 16:49, Leonid Vasiliev wrote: > From: Leonid <lvasiliev@tarantool.org> > > The policy for check of luarocks flags has been changed (moved from tarantoolctl to luarocks). Usually there is a high tolerance to too long commit message lines, but this is outstanding. Please, try to keep it in 80 symbols top, 66 best. > We had a white-list of luarocks options in tarantoolctl before. > Now we have a black-list of options (for tarantool) in luarocks. We don't have a blacklist anymore, from what I see. The not supported options were just removed from the options parser. > Help section has been updated. It was not. > @TarantoolBot document > Title: Update tarantoolctl rocks > tarantoolctl rocks commands has been added: > build > config > download > init > lint > new_version > purge > which > write_rockspec Where a technical writer should take documentation on these commands? Their arguments, options? Probably there is a link describing all of them? > Closes #4629 > --- > https://github.com/tarantool/tarantool/issues/4629 > https://github.com/tarantool/tarantool/tree/lvasiliev/gh-4629-forward-flags
next prev parent reply other threads:[~2020-04-10 0:00 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-05 14:49 Leonid Vasiliev 2020-04-09 6:55 ` lvasiliev 2020-04-10 0:00 ` Vladislav Shpilevoy [this message] 2020-04-10 9:10 ` lvasiliev 2020-04-11 14:11 ` Vladislav Shpilevoy 2020-04-12 17:12 ` lvasiliev 2020-04-13 12:03 ` lvasiliev 2020-04-12 20:15 ` Vladislav Shpilevoy -- strict thread matches above, loose matches on Subject: below -- 2019-11-19 8:56 Leonid
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=cbdb690e-7368-08ad-1bc8-fb387f3a2bdb@tarantool.org \ --to=v.shpilevoy@tarantool.org \ --cc=Yaroslav.dynnikov@tarantool.org \ --cc=lvasiliev@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v2] rocks: forward options to luarocks' \ /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