From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21333 invoked by alias); 30 Nov 2011 23:31:50 -0000 Received: (qmail 21324 invoked by uid 22791); 30 Nov 2011 23:31:50 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 30 Nov 2011 23:31:37 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 41C932BB12A; Wed, 30 Nov 2011 18:31:36 -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 nhNePZYplQ3Q; Wed, 30 Nov 2011 18:31:36 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 170582BB103; Wed, 30 Nov 2011 18:31:35 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 21678145615; Wed, 30 Nov 2011 18:31:20 -0500 (EST) Date: Wed, 30 Nov 2011 23:31:00 -0000 From: Joel Brobecker To: Sergio Durigan Junior Cc: Tom Tromey , GDB Development Subject: Re: ambiguous linespec decision point Message-ID: <20111130233120.GP26480@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.20 (2009-06-14) Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-11/txt/msg00138.txt.bz2 > I know my opinion does not count that much, but I think it is OK to > check it in since you both spent quite some time hunting and solving > bugs on this. Moreover, after the branching we would have two weeks > IIRC to find some regression and fix it. I think what I will do if the patch goes in is create the branch right after, and then wait a week before creating the first pre- release. And then plan for the official releasee 2 weeks later. That gives us a week to find potential bugs before we ask for wider testing... -- Joel