From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27912 invoked by alias); 2 Feb 2010 21:06:12 -0000 Received: (qmail 27902 invoked by uid 22791); 2 Feb 2010 21:06:12 -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) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 02 Feb 2010 21:06:05 +0000 Received: from int-mx08.intmail.prod.int.phx2.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.21]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o12L64fN017493 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 2 Feb 2010 16:06:04 -0500 Received: from localhost.localdomain (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx08.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id o12L632s030304 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Tue, 2 Feb 2010 16:06:04 -0500 Date: Sun, 21 Feb 2010 17:48:00 -0000 From: Kevin Buettner To: insight@sourceware.org Subject: Re: gdb/gdbtk not tagged with gdb_7_0-branch tag Message-ID: <20100202140603.2ff3232c@redhat.com> In-Reply-To: <4B68635E.6020906@redhat.com> References: <20100202065643.2117c127@redhat.com> <4B68635E.6020906@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact insight-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sourceware.org X-SW-Source: 2010-q1/txt/msg00022.txt.bz2 On Tue, 02 Feb 2010 09:39:42 -0800 Keith Seitz wrote: > So, yes, you may tag the sources. [Don't forget gdb/testsuite/gdb.gdbtk.] I've created the branch tag, gdb_7_0-branch, in the following locations: gdb/gdbtk gdb/testsuite/gdb.gdbtk tcl tk itcl libgui I did not create a (non-branch) gdb_7_0_branchpoint tag, though I can still do this if desired. I doubt that there will be enough changes put onto the insight portion of the branch for anyone to care... Also, creation of the branchpoint tag for insight has been erratic over the last several GDB releases. If a branchpoint tag is created, I recommend that it be given the name gdb_7_0-2009-09-16-branchpoint, even though that date isn't quite accurate for the tagging that I did. (I used "-D 2009-09-18" to check out the sources that I tagged. Insight often lags GDB on necessary fixes by a few days, so it seemed prudent to use a slightly later date.) I've done a test checkout of the insight sources using the gdb_7_0-branch branch tag. Insight builds and runs on my machine. Looking at Help->About GDB... shows the correct version number. I've not done any testing beyond making sure that the gui comes up when invoked. Kevin