This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Adding GDB branches to your nightly version updates...
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Alan Modra <amodra at gmail dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Wed, 4 Dec 2013 06:48:40 +0400
- Subject: Re: Adding GDB branches to your nightly version updates...
- Authentication-results: sourceware.org; auth=none
- References: <20131203074923 dot GK5193 at adacore dot com> <20131204004303 dot GE3306 at bubble dot grove dot modra dot org>
> 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