From: Alan Modra <amodra@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: Adding GDB branches to your nightly version updates...
Date: Wed, 04 Dec 2013 01:28:00 -0000 [thread overview]
Message-ID: <20131204012613.GH3306@bubble.grove.modra.org> (raw)
In-Reply-To: <8738m9juhx.fsf@igel.home>
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
next prev parent reply other threads:[~2013-12-04 1:28 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 [this message]
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=20131204012613.GH3306@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=schwab@linux-m68k.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