From: Alexandre Oliva <aoliva@redhat.com>
To: "Zack Weinberg" <zack@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org,
binutils@sourceware.org
Subject: Re: PATCH: replace obsolete GCC libintl with top-level libintl from newest gettext distribution
Date: Thu, 03 Jul 2003 15:20:00 -0000 [thread overview]
Message-ID: <orisqjhc7h.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <87he64wa7m.fsf@codesourcery.com>
On Jul 3, 2003, "Zack Weinberg" <zack@codesourcery.com> wrote:
> * ABOUT-NLS, config.rpath: Import from gettext 0.12.1.
I'm disgusted at the duplication of outdated code from libtool in
config.rpath, and about other assumptions about libtool in intl's
autoconf macros. However, none of this is your fault, so, unless
we try to get upstream gettext to avoid this, we'll have to go with
the flow.
Unless others bring up any further issues, or think we should stick
with the old version of intl that is present in the src tree, please
go ahead and check the whole thing in. Thanks for doing this.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer
next prev parent reply other threads:[~2003-07-03 15:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-03 3:40 Zack Weinberg
2003-07-03 3:46 ` Andrew Pinski
2003-07-03 3:48 ` Zack Weinberg
2003-07-03 15:20 ` Alexandre Oliva [this message]
2003-07-03 15:48 ` Zack Weinberg
2003-07-03 18:25 ` Alexandre Oliva
2003-07-03 18:35 ` Zack Weinberg
2003-07-03 15:22 ` Alexandre Oliva
2003-07-03 15:46 ` Zack Weinberg
2003-07-03 16:48 ` Zack Weinberg
2003-07-03 18:23 ` Alexandre Oliva
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=orisqjhc7h.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@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