From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27520 invoked by alias); 25 Dec 2013 02:47:43 -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 27508 invoked by uid 89); 25 Dec 2013 02:47:41 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.1 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Wed, 25 Dec 2013 02:47:40 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id A4A701166A4; Tue, 24 Dec 2013 21:47:38 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id pftJ0qS0RlkL; Tue, 24 Dec 2013 21:47:38 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 28165116694; Tue, 24 Dec 2013 21:47:38 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 98D85E07B7; Wed, 25 Dec 2013 06:47:33 +0400 (RET) Date: Wed, 25 Dec 2013 02:47:00 -0000 From: Joel Brobecker To: Nick Bull Cc: "gdb-patches@sourceware.org" Subject: Re: GDB 7.7 branching on Monday? Message-ID: <20131225024733.GH4605@adacore.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-SW-Source: 2013-12/txt/msg00960.txt.bz2 > Is it possible to get this Python events patch in under the wire? > > http://sourceware.org/ml/gdb-patches/2013-12/msg00505.html > > It's been through a couple of rounds of review and has no outstanding > issues that I know of. I'd love to get this one in 7.7, but at the same time, it's hard justifying delaying a branch for a non-critical failure. The good news is that there is little to no activity at the moment, so there is no point in me creating the branch now. Creating it after New Year will prevent the need for updating the year ranges in the copyright headers twice. And that will give you more time to get the patch in. I took a quick look at your patch; one of the trivial things I noticed is that many new functions and new types are missing documentation. If you add those and resend a patch, that'll have the nice property if implicitly pinging the maintainers. Also, feel free to ping on your patch a week or two after submission, and every week thereafter. -- Joel