From: Phil Edwards <phil@jaj.com>
To: Zack Weinberg <zack@codesourcery.com>
Cc: Andrew Cagney <ac131313@redhat.com>,
gcc@gcc.gnu.org, binutils@sourceware.org, gdb@sourceware.org
Subject: Re: RFC: Moving gcc/intl to toplevel; syncing both copies to 0.12.1
Date: Wed, 02 Jul 2003 17:59:00 -0000 [thread overview]
Message-ID: <20030702175955.GA13951@disaster.jaj.com> (raw)
In-Reply-To: <873choyfse.fsf@codesourcery.com>
On Wed, Jul 02, 2003 at 10:55:29AM -0700, Zack Weinberg wrote:
>
> I could do that; it will mean that for one week people who construct
> combined trees have to be careful with the intl directory, but that
> should be ok, yes?
Depends on what "careful" means. If it's just a matter of always using
the GCC copy, that should be fine.
--
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace. We seek
not your counsel, nor your arms. Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen. - Samuel Adams
next prev parent reply other threads:[~2003-07-02 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 17:07 Zack Weinberg
2003-07-02 17:49 ` Andrew Cagney
2003-07-02 17:56 ` Zack Weinberg
2003-07-02 17:59 ` Phil Edwards [this message]
2003-07-03 16:01 ` Andrew Cagney
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=20030702175955.GA13951@disaster.jaj.com \
--to=phil@jaj.com \
--cc=ac131313@redhat.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=zack@codesourcery.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