From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id A060D23453 for ; Wed, 24 Jul 2019 04:00:15 -0400 (EDT) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FIzNr6mMreQe for ; Wed, 24 Jul 2019 04:00:15 -0400 (EDT) Received: from smtp57.i.mail.ru (smtp57.i.mail.ru [217.69.128.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTPS id 582A420EF1 for ; Wed, 24 Jul 2019 04:00:15 -0400 (EDT) Date: Wed, 24 Jul 2019 11:00:09 +0300 From: Kirill Yukhin Subject: [tarantool-patches] Re: [PATCH] Output of fiber.info will contain only non-idle fibers Message-ID: <20190724080009.l37vvopimxjdqs5h@tarantool.org> References: <20190723195643.GA18567@atlas> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190723195643.GA18567@atlas> Sender: tarantool-patches-bounce@freelists.org Errors-to: tarantool-patches-bounce@freelists.org Reply-To: tarantool-patches@freelists.org List-Help: List-Unsubscribe: List-software: Ecartis version 1.0.0 List-Id: tarantool-patches List-Subscribe: List-Owner: List-post: List-Archive: To: tarantool-patches@freelists.org Cc: georgy@tarantool.org Hello, On 23 Jul 22:56, Konstantin Osipov wrote: > * Maria K [19/07/23 21:01]: > > The output used to be too cluttered due to idle ones. > > > > Closes #4235 > > @kyukhin, first, please I don't get how does this get scheduled to a > milestone? How does this follow triage guidelines? I won't ever discuss any internal documents publicly, sorry. I believe this contradicts ethitcs. That is second time you doing this, please stop. > Please don't schedule anything that is not a priority, even if > it's a noob issue, since it takes time of everyone involved. That was a customer request. If you'd like not to review the patch - feel free to just skip it, we'll find another reviewer. -- Regards, Kirill Yukhin