From: Steve Ellcey <sje@cup.hp.com>
To: ian@airs.com
Cc: binutils@sourceware.org, gdb@sourceware.org, gcc@gcc.gnu.org
Subject: Re: intl directory: gcc vs. src
Date: Tue, 16 May 2006 23:23:00 -0000 [thread overview]
Message-ID: <200605162236.PAA29498@hpsje.cup.hp.com> (raw)
In-Reply-To: <m3wtcr6be8.fsf@gossamer.airs.com>
> > What do people who build in a combined tree do with intl? Do they use
> > the GCC version or the src tree version? Is there any consensus about
> > whether or not there should be a single version of intl, and if so,
> > which one should be used?
>
> Yes, there should be a single version of intl. I don't think anybody
> cares which version is used, as long as it works. If you have taken
> the time to test a unified intl, and are prepared to fix any problems,
> I think your patch would be great.
>
> Ian
OK, I can sign up for that. While looking at the changes needed for the
text in the MAINTAINERS file, I saw the following entry for libiberty:
| libiberty/; libiberty's part of include/
| gcc: http://gcc.gnu.org
| Changes need to be done in tandem with the official GCC
| sources or submitted to the master file maintainer and brought
| in via a merge. Note: approved patches in gcc's libiberty
| are automatically approved in this libiberty also; feel free
| to merge them yourself if needed sooner than the next merge.
| Otherwise, changes are automatically merged, usually within
| a day.
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?
Steve Ellcey
sje@cup.hp.com
next prev parent reply other threads:[~2006-05-16 22:37 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 [this message]
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
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=200605162236.PAA29498@hpsje.cup.hp.com \
--to=sje@cup.hp.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=ian@airs.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).