From: DJ Delorie <dj@redhat.com>
To: sje@cup.hp.com
Cc: ian@airs.com, binutils@sourceware.org, gdb@sourceware.org,
gcc@gcc.gnu.org
Subject: Re: intl directory: gcc vs. src
Date: Wed, 17 May 2006 00:41:00 -0000 [thread overview]
Message-ID: <200605162245.k4GMj9EY024243@greed.delorie.com> (raw)
In-Reply-To: <200605162236.PAA29498@hpsje.cup.hp.com> (message from Steve Ellcey on Tue, 16 May 2006 15:36:22 -0700 (PDT))
> Who maintains this automatic merge process?
Me. I have a cron job that checks out gcc's and src's libiberty and
include, compares them, copies any differing files to src, and sends
me email. I then run a "do it" script to do the actual commit.
There's not much advantage in using this setup for an initial merge
(it would take as much effort to set it up as it would to just do the
merge). It's much more useful as an ongoing merge system.
next prev parent reply other threads:[~2006-05-16 22:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 0:23 Steve Ellcey
2006-05-12 20:04 ` Ian Lance Taylor
2006-05-16 23:23 ` Steve Ellcey
2006-05-17 0:35 ` Daniel Jacobowitz
2006-05-17 11:05 ` Steve Ellcey
2006-05-17 13:21 ` Daniel Jacobowitz
2006-05-17 0:41 ` DJ Delorie [this message]
2006-05-17 1:27 ` Bobby McNulty
2006-05-17 5:09 ` DJ Delorie
2006-05-15 23:09 ` James Lemke
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=200605162245.k4GMj9EY024243@greed.delorie.com \
--to=dj@redhat.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=ian@airs.com \
--cc=sje@cup.hp.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).