From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp44.i.mail.ru (smtp44.i.mail.ru [94.100.177.104]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id 02E1C4696C3 for ; Sun, 12 Apr 2020 20:25:35 +0300 (MSK) References: <865fb768-3c90-ec8e-96cf-7d7598a9f6e0@tarantool.org> <711c06ec-7953-fcb0-f0cd-a1b68a37e8ae@tarantool.org> From: lvasiliev Message-ID: Date: Sun, 12 Apr 2020 20:25:34 +0300 MIME-Version: 1.0 In-Reply-To: <711c06ec-7953-fcb0-f0cd-a1b68a37e8ae@tarantool.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [Tarantool-patches] [PATCH v3 0/2] Adapt luarocks for tarantoolctl List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vladislav Shpilevoy , Yaroslav Dynnikov Cc: tarantool-patches@dev.tarantool.org On 11.04.2020 17:23, Vladislav Shpilevoy wrote: >> As of the second one ("Delete flags which can't be used with >> tarantoolctl rocks" 1b51b2f ), I'm worried that our fork every day goes >> farther from upstream. You didn't say a word about necessity to /remove/ >> it, but it looks like another postponed problem. > > Leonid, btw, why do we remove them, again? I was always thinking it > is a part of the ticket, but I don't see it there except in your > comments. Because after talking with Yaroslav, we decided that the user should not be able to use these flags. When I worked on task, I was still too young and did not know that all summaries of discussions should be written down in comments on task.