From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60646) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gKpMW-0002t3-7q for qemu-devel@nongnu.org; Thu, 08 Nov 2018 13:49:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gKpMN-0006Ow-JQ for qemu-devel@nongnu.org; Thu, 08 Nov 2018 13:49:00 -0500 Received: from mail-wr1-f65.google.com ([209.85.221.65]:44192) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gKpMN-00060j-8C for qemu-devel@nongnu.org; Thu, 08 Nov 2018 13:48:55 -0500 Received: by mail-wr1-f65.google.com with SMTP id j17-v6so17248805wrq.11 for ; Thu, 08 Nov 2018 10:48:42 -0800 (PST) MIME-Version: 1.0 References: <20181108143422.15955-1-philmd@redhat.com> <20181108171716.GN12503@habkost.net> <5f495bd7-8489-4e8f-8fd5-d0bb28787fa4@redhat.com> <87o9azjtqm.fsf@dusky.pond.sub.org> In-Reply-To: <87o9azjtqm.fsf@dusky.pond.sub.org> From: =?UTF-8?Q?Philippe_Mathieu=2DDaud=C3=A9?= Date: Thu, 8 Nov 2018 19:48:29 +0100 Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH] scripts: Remove unused python imports List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Markus Armbruster Cc: Peter Maydell , Cleber Rosa , Eduardo Habkost , Stefan Hajnoczi , QEMU Developers On Thu, Nov 8, 2018 at 7:43 PM Markus Armbruster wrote: > Peter Maydell writes: > > On 8 November 2018 at 18:08, Philippe Mathieu-Daud=C3=A9 wrote: > >> Anyway there are no information about merge window in the wiki. > >> When I started it was not easy to understand it and why patches sent w= hen > >> 'merge window is close' fall under the crap and are unnoticed, thus it= is > >> better to wait before to send, or resend them. > > > > The intention (not always something we succeed at) is that > > maintainers should respond to patches, do review, etc, at > > any point in our release cycle. During a release they might > > reply to say "I won't get to reviewing this for a little while" > > or "I'll take this patch once the trunk reopens for releases", > > In both cases, the maintainer remains responsible for tracking the > patches. > > I believe the sane thing to do is to review patches as usual, and to > queue the ones that are ready to go into the next release on a separate > branch. > > > but they shouldn't just leave patch submitters with no response > > at all... > > Yes, that's rude. Thanks both to clarify your maintainer view. I added this thread to my TODO and if nobody write about this in the wiki I'll, but later. Phil.