From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> To: Yaroslav Dynnikov <yaroslav.dynnikov@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH v3 0/2] Adapt luarocks for tarantoolctl Date: Sat, 11 Apr 2020 16:23:49 +0200 [thread overview] Message-ID: <711c06ec-7953-fcb0-f0cd-a1b68a37e8ae@tarantool.org> (raw) In-Reply-To: <CAK0MaD27MC9NSKi8_8eUz3B0uZOA3QfNzSmsTz+eT86Rdg3TNQ@mail.gmail.com> > On 10/04/2020 19:02, Yaroslav Dynnikov wrote: > Hi, Leonid. > > The first patch ("Add the chdir option for make" 8e8db7f <https://github.com/tarantool/luarocks/commit/8e8db7f255a855c585245c288414ceb097576e07>) looks good to > me. I hope you'll be able to find time and propose it to upstream, in my > opinion it'll helpful there too. > > As of the second one ("Delete flags which can't be used with > tarantoolctl rocks" 1b51b2f <https://github.com/tarantool/luarocks/commit/1b51b2fe1c194719a7a8a74220a954a91c21f2a7>), 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. > Luarocks version is > already 3.3.1, while we still basing 3.1.1. And every such commit makes > it harder to rebase. > > The last time we were upgrading luarocks we've spent several weeks of > worktime to resolve all the problems. And, disappointingly, those > changes weren't merged to 1.10, so my colleagues usually come back with > the same problems as 2 years ago. Please, don't screw over our future > selves. While we sure should be as close to the upstream as possible, I think the rebase problem will appear always when you do any patches, and rebase once per 100 years.
next prev parent reply other threads:[~2020-04-11 14:23 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-09 6:33 Leonid Vasiliev 2020-04-09 6:33 ` [Tarantool-patches] [PATCH v3 1/2] Add the chdir option for make Leonid Vasiliev 2020-04-09 6:33 ` [Tarantool-patches] [PATCH v3 2/2] Delete flags which can't be used with tarantoolctl rocks Leonid Vasiliev 2020-04-13 11:59 ` lvasiliev 2020-04-13 12:16 ` Yaroslav Dynnikov 2020-04-10 0:00 ` [Tarantool-patches] [PATCH v3 0/2] Adapt luarocks for tarantoolctl Vladislav Shpilevoy 2020-04-10 8:41 ` lvasiliev 2020-04-10 17:02 ` Yaroslav Dynnikov 2020-04-10 18:37 ` lvasiliev 2020-04-11 14:23 ` Vladislav Shpilevoy [this message] 2020-04-12 17:25 ` lvasiliev 2020-04-12 18:30 ` Yaroslav Dynnikov 2020-04-12 19:52 ` Vladislav Shpilevoy 2020-04-13 7:44 ` lvasiliev 2020-04-13 11:07 ` lvasiliev
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=711c06ec-7953-fcb0-f0cd-a1b68a37e8ae@tarantool.org \ --to=v.shpilevoy@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --cc=yaroslav.dynnikov@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v3 0/2] Adapt luarocks for tarantoolctl' \ /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