From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf1-f65.google.com (mail-lf1-f65.google.com [209.85.167.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id A2EB14696C3 for ; Fri, 17 Apr 2020 10:10:24 +0300 (MSK) Received: by mail-lf1-f65.google.com with SMTP id r17so968230lff.2 for ; Fri, 17 Apr 2020 00:10:24 -0700 (PDT) Date: Fri, 17 Apr 2020 10:10:21 +0300 From: Cyrill Gorcunov Message-ID: <20200417071021.GV3072@uranus> References: <20200416120658.33777-1-sergepetrenko@tarantool.org> <20200416123802.GS3072@uranus> <20200416124240.GT3072@uranus> <20200417070227.kjdavtfhyaykfevf@tarantool.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200417070227.kjdavtfhyaykfevf@tarantool.org> Subject: Re: [Tarantool-patches] [PATCH] relay: move relay_schedule_pending_gc before status List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kirill Yukhin Cc: tarantool-patches@dev.tarantool.org, v.shpilevoy@tarantool.org On Fri, Apr 17, 2020 at 10:02:27AM +0300, Kirill Yukhin wrote: > > > > > > Maybe it worth to have two commits? > > > > > > - use vclock_compare_ignore0 in relay_schedule_pending_gc > > > - reorder relay_schedule_pending_gc > > > > Doesn't matter, already merged :) > > I have no idea, why my mail wasn't sent. > > Anyway, the patch was committed to master. No, I've been replying and then found that you've already merged the patch. IOW you msg been delivered properly. That's why I said "already merged".