From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17913 invoked by alias); 18 Apr 2013 00:19:23 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 17903 invoked by uid 89); 18 Apr 2013 00:19:22 -0000 X-Spam-SWARE-Status: No, score=-8.0 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.1 Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Thu, 18 Apr 2013 00:19:21 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r3I0JJYM026408 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 17 Apr 2013 20:19:19 -0400 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r3I0JHWR022422; Wed, 17 Apr 2013 20:19:18 -0400 Message-ID: <516F3C05.2030603@redhat.com> Date: Thu, 18 Apr 2013 15:16:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130311 Thunderbird/17.0.4 MIME-Version: 1.0 To: Yao Qi CC: gdb-patches@sourceware.org Subject: Re: [ping 2]: [PATCH v4 0/5] MI notification on trace started/stopped References: <1358838232-13319-1-git-send-email-yao@codesourcery.com> <1364869917-12803-1-git-send-email-yao@codesourcery.com> <5164D38C.8070003@codesourcery.com> <516E3ED7.5080204@codesourcery.com> In-Reply-To: <516E3ED7.5080204@codesourcery.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2013-04/txt/msg00557.txt.bz2 I do my best to review as much as possible. In fact, my main projects keep getting delayed for months as I can't ever find enough time/energy to focus on them. Unfortunately it tends to happen that I end up needing to spend a very significant amount of time and energy through the patches/proposals. The past weeks were a set back, as as you know, 7.6 had issues that needed addressing. It'd be great if patches/designs and submissions come up perfect from the get go, or that I was smarter and could review faster, but that's unfortunately not frequently the case. The bigger the patch/series, the more likely it is that it needs iteration. I know you have several series waiting to get in. Please be patient. If you look at CS submissions as a whole, you'll notice that I'm usually reviewing/iterating over at least one at a given time. It's just that bigger ones require more energy, so they take more to get through. Next up, as I said before, is the range stepping series. Please let me focus on it and get it to completion, and context switch to the async notifications afterwards. Thanks, -- Pedro Alves