Adding GDB branches to your nightly version updates...

Adding GDB branches to your nightly version updates...

[Joel Brobecker]

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

Re: Adding GDB branches to your nightly version updates...

[Alan Modra]

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

Re: Adding GDB branches to your nightly version updates...

[Andreas Schwab]

Alan Modra <amodra@gmail.com> writes:

> 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. :)

There's also git new-workdir.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: Adding GDB branches to your nightly version updates...

[Alan Modra]

On Wed, Dec 04, 2013 at 02:05:30AM +0100, Andreas Schwab wrote:
> Alan Modra <amodra@gmail.com> writes:
> 
> > 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. :)
> 
> There's also git new-workdir.

Thanks!  That looks much better than my cp -al.

-- 
Alan Modra
Australia Development Lab, IBM

Re: Adding GDB branches to your nightly version updates...

[Joel Brobecker]

> 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. :)

Thanks, Alan.

If the repository is kept clean (no un-comitted) changes, you can
just do "git checkout <branch_name>" (where branch_name would be
"master", or the binutils active branch, or GDB's active branch).
With git, branch changes are really fast.

On the other hand, we might want to keep all commits as close as
possible to the midnight mark, so that we don't have to delay too
much the GDB scripts. If we use multiple copies of the repo, we
avoid the time it takes to switch between branch, which takes,
on my laptop, between 1 and 3 seconds.

But on the other hand of the other hand, we already have the delay
it takes to fetch new changes, and unless your script was programmed
to fetch only the branch you want, you'd be fetching the same data
3 times, which can add to the delay.

The bottom line is that I'm thinking way too much into this, and that
you probably don't really have any real reason to change a thing :).

Is the script running on sourceware? If you'd like, we can share
responsibility of the script, and help out with the git part.

-- 
Joel