From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13536 invoked by alias); 3 Dec 2013 07:49:36 -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 13527 invoked by uid 89); 3 Dec 2013 07:49:36 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.9 required=5.0 tests=AWL,BAYES_50,RDNS_NONE 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; Tue, 03 Dec 2013 07:49:35 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 02A9E11684B; Tue, 3 Dec 2013 02:50:05 -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 gXPUmYG74aCS; Tue, 3 Dec 2013 02:50:04 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 8FCBD116845; Tue, 3 Dec 2013 02:50:04 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id DDB08E081D; Tue, 3 Dec 2013 11:49:23 +0400 (RET) Date: Tue, 03 Dec 2013 07:49:00 -0000 From: Joel Brobecker To: Alan Modra Cc: gdb-patches@sourceware.org Subject: Adding GDB branches to your nightly version updates... Message-ID: <20131203074923.GK5193@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-SW-Source: 2013-12/txt/msg00069.txt.bz2 Hi Alan, The GDB project is going to create the GDB 7.7 release branch fairly soon, within the next couple of weeks, I would say. Up until recently, the date in GDB's version number was handled directly in GDB, but we recently switched to using bfd's version.h instead. Once we cut the 7.7 branch, we'll need the date updated on that branch as well. I am wondering how you'd like to proceed. The simplest would probably for you and I to coordinate so that I can let you know when the active branch changes. Another option, if we'd like to avoid depending on each other, is for us to do the update on the branch ourselves. But I think it would be a shame to be doing so. One final option that occured to me is to move your script to sourceware, and get the update done there. Both of us can then adjust the active branch whenever necessary. WDYT? Thanks, -- Joel