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


      parent reply	other threads:[~2013-12-04  2:48 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
2013-12-04  1:05   ` Andreas Schwab
2013-12-04  1:28     ` Alan Modra
2013-12-04  2:48   ` Joel Brobecker [this message]

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=20131204024840.GF3114@adacore.com \
    --to=brobecker@adacore.com \
    --cc=amodra@gmail.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