From: DJ Delorie <dj@redhat.com>
To: sje@cup.hp.com
Cc: binutils@sourceware.org, gdb@sourceware.org, drow@false.org,
gcc@gcc.gnu.org, ian@airs.com
Subject: Re: PATCH: Update src/intl from gcc/intl
Date: Fri, 19 May 2006 21:16:00 -0000 [thread overview]
Message-ID: <200605191920.k4JJKOlX019452@greed.delorie.com> (raw)
In-Reply-To: <200605191757.KAA08389@hpsje.cup.hp.com> (message from Steve Ellcey on Fri, 19 May 2006 10:57:50 -0700 (PDT))
> I will unless you want to add this to the libiberty merge you do now.
I don't mind adding it to my script, if people agree that's what they
want. It's just that nobody asked :-P
next prev parent reply other threads:[~2006-05-19 19:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-19 15:57 Steve Ellcey
2006-05-19 16:30 ` Nick Clifton
2006-05-19 17:17 ` Daniel Jacobowitz
2006-05-19 17:57 ` DJ Delorie
2006-05-19 21:16 ` Steve Ellcey
2006-05-19 21:16 ` DJ Delorie [this message]
2006-05-21 14:14 ` Mark Mitchell
2006-05-22 22:37 ` DJ Delorie
2006-05-22 17:59 ` Steve Ellcey
2006-05-23 1:14 ` DJ Delorie
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=200605191920.k4JJKOlX019452@greed.delorie.com \
--to=dj@redhat.com \
--cc=binutils@sourceware.org \
--cc=drow@false.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=ian@airs.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