From: DJ Delorie <dj@redhat.com>
To: sje@cup.hp.com
Cc: drow@false.org, ian@airs.com, mark@codesourcery.com,
binutils@sourceware.org, gdb@sourceware.org
Subject: Re: PATCH: Update src/intl from gcc/intl
Date: Mon, 22 May 2006 23:47:00 -0000 [thread overview]
Message-ID: <200605221756.k4MHuCHN001613@greed.delorie.com> (raw)
In-Reply-To: <200605221538.IAA10884@hpsje.cup.hp.com> (message from Steve Ellcey on Mon, 22 May 2006 08:38:56 -0700 (PDT))
> I have updated the intl directory to match the GCC directory so if
> you could add that to your libiberty merge process that would be
> great. I also copied config.rpath over at the top level so that
> should be added too.
All set.
prev parent reply other threads:[~2006-05-22 17:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-19 17:50 Steve Ellcey
2006-05-19 17:57 ` Nick Clifton
2006-05-19 18:06 ` Daniel Jacobowitz
2006-05-19 18:50 ` DJ Delorie
2006-05-19 19:22 ` Steve Ellcey
2006-05-20 12:43 ` DJ Delorie
2006-05-20 13:58 ` Mark Mitchell
2006-05-22 22:37 ` DJ Delorie
2006-05-22 20:39 ` Steve Ellcey
2006-05-22 23:47 ` DJ Delorie [this message]
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=200605221756.k4MHuCHN001613@greed.delorie.com \
--to=dj@redhat.com \
--cc=binutils@sourceware.org \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=ian@airs.com \
--cc=mark@codesourcery.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).