From: DJ Delorie <dj@redhat.com>
To: ian@wasabisystems.com
Cc: binutils@sourceware.org, gdb@sourceware.org
Subject: Re: gcc/intl vs. src/intl
Date: Wed, 17 Nov 2004 03:28:00 -0000 [thread overview]
Message-ID: <200411170211.iAH2B3s2031142@greed.delorie.com> (raw)
In-Reply-To: <m3vfc5p7ge.fsf@gossamer.airs.com> (message from Ian Lance Taylor on 16 Nov 2004 20:53:05 -0500)
> Presumably the long-term fix would to keep intl in sync as we keep
> libiberty in sync.
Note: the key to doing this is automatically to let one repository
(presumably, src) relinquish control of src/intl to the other (gcc),
so that the sync scripts only have to work one way. We do this for
libiberty.
Keeping them in sync automatically is not practical if patches are
allowed on both sides. This is the case for toplevel.
next prev parent reply other threads:[~2004-11-17 2:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 2:11 Ian Lance Taylor
2004-11-17 3:28 ` DJ Delorie [this message]
2004-11-17 14:25 ` Christopher Faylor
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=200411170211.iAH2B3s2031142@greed.delorie.com \
--to=dj@redhat.com \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
--cc=ian@wasabisystems.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