From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13942 invoked by alias); 2 Dec 2013 07:49:34 -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 13933 invoked by uid 89); 2 Dec 2013 07:49:33 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.8 required=5.0 tests=AWL,BAYES_50,RDNS_NONE,URIBL_BLOCKED autolearn=no version=3.3.2 X-HELO: rock.gnat.com Received: from Unknown (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Mon, 02 Dec 2013 07:49:32 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 062EE116801; Mon, 2 Dec 2013 02:50:02 -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 TyMAi6M08ltY; Mon, 2 Dec 2013 02:50:01 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 77163116800; Mon, 2 Dec 2013 02:50:01 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 70F6BE0697; Mon, 2 Dec 2013 11:49:20 +0400 (RET) Date: Mon, 02 Dec 2013 07:49:00 -0000 From: Joel Brobecker To: Jan Kratochvil Cc: gdb-patches@sourceware.org, Philippe Waroquiers , Doug Evans Subject: Re: status update for GDB 7.7? Message-ID: <20131202074920.GT3114@adacore.com> References: <20131202035637.GQ3114@adacore.com> <20131202073623.GA13911@host2.jankratochvil.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131202073623.GA13911@host2.jankratochvil.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-SW-Source: 2013-12/txt/msg00018.txt.bz2 > It is not checked in. The patch is IMO done in the link above. > > Just Doug required some whole new feature/patchset just because of the > testcase there and currently I work on other more urgent things: > https://sourceware.org/ml/gdb-patches/2013-10/msg00287.html OK. So what do you guys want to do with respect to the release? Some possible options: (1) Defer the patch for the next release, hoping there will be more time to look into the new ideas? (2) Or defer the release while waiting for someone to find that time? (3) Commit the patch as is, and defer the new improvement for later? Any other suggestions? From my vantage point, it sounds like we have let, in this thread, best be the enemy of good. IIUC, the patch is OK, but blocked because we could do better in the testcase? Or did a small issue in the testcase raise a bigger issue? -- Joel