From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3413 invoked by alias); 23 Feb 2010 23:59:21 -0000 Received: (qmail 3396 invoked by uid 22791); 23 Feb 2010 23:59:20 -0000 X-SWARE-Spam-Status: No, hits=-6.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_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, 23 Feb 2010 23:59:16 +0000 Received: from int-mx04.intmail.prod.int.phx2.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.17]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o1NNxFsc013668 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 23 Feb 2010 18:59:15 -0500 Received: from localhost.localdomain (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx04.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id o1NNxExX005971 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Tue, 23 Feb 2010 18:59:14 -0500 Date: Mon, 08 Mar 2010 21:54:00 -0000 From: Kevin Buettner To: insight@sourceware.org Subject: Branch tag gdb_7_1-branch added for insight-specific sources Message-ID: <20100223165914.447b1da2@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/msg00027.txt.bz2 I've tagged the insight-specific sources with the branch tag, gdb_7_1-branch. Specifically, I've tagged the following directories: gdb/gdbtk gdb/testsuite/gdb.gdbtk tcl tk itcl libgui The rest of the GDB sources have already been tagged with gdb_7_1-branch. Now that the insight-specific sources have also been tagged, it is possible to check out insight using this the tag and obtain a tree from which insight may be built. I've done a test check out and build to verify that it can indeed be done. The version number displayed by Help->About GDB... is correct. (I haven't done any testing beyond this simple smoke test.) I did not create a branch point tag, but can do so if desired. (Let me know within the next few days...) If a branch point tag is desired, it should be named gdb_7_1-2010-02-18-branchpoint in order to match the rest of GDB. The date won't be quite right, but will be close enough, and, IMO, it is more important that it match the tag used by the rest of GDB. Kevin