Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Alan Modra <amodra@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Adding GDB branches to your nightly version updates...
Date: Wed, 04 Dec 2013 00:43:00 -0000	[thread overview]
Message-ID: <20131204004303.GE3306@bubble.grove.modra.org> (raw)
In-Reply-To: <20131203074923.GK5193@adacore.com>

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


  reply	other threads:[~2013-12-04  0:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-03  7:49 Joel Brobecker
2013-12-04  0:43 ` Alan Modra [this message]
2013-12-04  1:05   ` Andreas Schwab
2013-12-04  1:28     ` Alan Modra
2013-12-04  2:48   ` Joel Brobecker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131204004303.GE3306@bubble.grove.modra.org \
    --to=amodra@gmail.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox