From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4550 invoked by alias); 4 Dec 2013 00:43:17 -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 4538 invoked by uid 89); 4 Dec 2013 00:43:16 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.1 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,RDNS_NONE,SPF_PASS autolearn=no version=3.3.2 X-HELO: mail-pd0-f182.google.com Received: from Unknown (HELO mail-pd0-f182.google.com) (209.85.192.182) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Wed, 04 Dec 2013 00:43:16 +0000 Received: by mail-pd0-f182.google.com with SMTP id v10so21329926pde.27 for ; Tue, 03 Dec 2013 16:43:08 -0800 (PST) X-Received: by 10.68.235.72 with SMTP id uk8mr42101202pbc.93.1386117788442; Tue, 03 Dec 2013 16:43:08 -0800 (PST) Received: from bubble.grove.modra.org ([101.166.26.37]) by mx.google.com with ESMTPSA id qf7sm151555373pac.14.2013.12.03.16.43.06 for (version=TLSv1.1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 03 Dec 2013 16:43:07 -0800 (PST) Received: by bubble.grove.modra.org (Postfix, from userid 1000) id 7A750EA008C; Wed, 4 Dec 2013 11:13:03 +1030 (CST) Date: Wed, 04 Dec 2013 00:43:00 -0000 From: Alan Modra To: Joel Brobecker Cc: gdb-patches@sourceware.org Subject: Re: Adding GDB branches to your nightly version updates... Message-ID: <20131204004303.GE3306@bubble.grove.modra.org> References: <20131203074923.GK5193@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131203074923.GK5193@adacore.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-SW-Source: 2013-12/txt/msg00110.txt.bz2 On Tue, Dec 03, 2013 at 11:49:23AM +0400, Joel Brobecker wrote: > 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. I'm happy to do that, but don't be surprised at the occasional glitch. I'm still learning the ropes with git.. For example, I keep two virgin copies of the repository just for the cron job that updates version.h in master and binutils-2_24-branch. I'm sure I could do with just one copy, but cp -al seemed easy at the time. :) -- Alan Modra Australia Development Lab, IBM