From: Daniel Jacobowitz <drow@false.org>
To: Steve Ellcey <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:35:00 -0000 [thread overview]
Message-ID: <20060516223900.GA16291@nevyn.them.org> (raw)
In-Reply-To: <200605162236.PAA29498@hpsje.cup.hp.com>
On Tue, May 16, 2006 at 03:36:22PM -0700, Steve Ellcey wrote:
> Can someone tell me about this automatic merge? I was going to submit a
> formal patch to change the contents of src/intl but it seems that if we
> have an automatic merge to copy libiberty from gcc to src, we could do
> the same for intl (and src/config.rhost) and then I wouldn't need to do
> any actual checkins for those changes. If we can do that then the only
> thing I would need to change by hand would be the intl text that is in
> the MAINTAINERS file.
>
> Who maintains this automatic merge process?
The man to ask about this is DJ Delorie. I'm not sure how much work it
is on his part, though.
Either way it would probably be best to do the initial sync by hand.
And is it really plausible that nothing in src would need updating for
the new intl?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-05-16 22:39 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 [this message]
2006-05-17 11:05 ` Steve Ellcey
2006-05-17 13:21 ` Daniel Jacobowitz
2006-05-17 0:41 ` DJ Delorie
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=20060516223900.GA16291@nevyn.them.org \
--to=drow@false.org \
--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).