From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19607 invoked by alias); 8 Apr 2009 16:26:27 -0000 Received: (qmail 19565 invoked by uid 22791); 8 Apr 2009 16:26:24 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 08 Apr 2009 16:26:12 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n38GQAst018639 for ; Wed, 8 Apr 2009 12:26:10 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n38GQF7r006377 for ; Wed, 8 Apr 2009 12:26:15 -0400 Received: from opsy.redhat.com (vpn-14-2.rdu.redhat.com [10.11.14.2]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n38GQAB5003997; Wed, 8 Apr 2009 12:26:10 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id 1EAAD3781B3; Wed, 8 Apr 2009 10:26:08 -0600 (MDT) To: Eli Zaretskii Cc: Vladimir Prus , gdb-patches@sources.redhat.com Subject: Re: Implement -exec-jump References: <200904080950.16691.vladimir@codesourcery.com> <200904081108.17248.vladimir@codesourcery.com> <837i1v627o.fsf@gnu.org> <200904081136.09957.vladimir@codesourcery.com> <8363hf5xsc.fsf@gnu.org> From: Tom Tromey Reply-To: tromey@redhat.com Date: Wed, 08 Apr 2009 16:26:00 -0000 In-Reply-To: <8363hf5xsc.fsf@gnu.org> (Eli Zaretskii's message of "Wed\, 08 Apr 2009 11\:56\:19 +0300") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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 X-SW-Source: 2009-04/txt/msg00149.txt.bz2 >>>>> "Eli" == Eli Zaretskii writes: Vladimir> I though there's "in a published release" somewhere in the Vladimir> above statement. Eli> That's exactly the point: the release of GDB 7.0 is quite close. Eli> Since we don't have any means to track such issues, you are now Eli> effectively asking me to somehow make sure the appropriate Eli> documentation patch is committed before the release, preferably before Eli> the branch. If we want, we can use Bugzilla to track release blockers. There are a few options for the mechanics of this. In this particular case, I'd imagine that the documentation patch is not much longer than the Bugzilla entry though :-) Tom