From: DJ Delorie <dj@redhat.com>
To: jakub@redhat.com
Cc: drow@codesourcery.com, binutils@sourceware.org, sje@cup.hp.com,
gdb-patches@sourceware.org, rda@sourceware.org
Subject: Re: changes in 'intl'
Date: Mon, 17 Jul 2006 20:07:00 -0000 [thread overview]
Message-ID: <200607172002.k6HK2t4X025897@greed.delorie.com> (raw)
In-Reply-To: <20060717161901.GZ3823@sunsite.mff.cuni.cz> (message from Jakub Jelinek on Mon, 17 Jul 2006 18:19:02 +0200)
> Fixed thusly, ok to commit (shall that be committed to both gcc and src
> trunk)?
Ok.
> 2006-07-17 Jakub Jelinek <jakub@redhat.com>
>
> * Makefile.def: Add dependencies for configure-opcodes
> on configure-intl and all-opcodes on all-intl.
> * Makefile.in: Regenerated.
prev parent reply other threads:[~2006-07-17 20:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4475B7AD.46E1073E@dessent.net>
[not found] ` <20060525144537.GA1017@nevyn.them.org>
[not found] ` <20060525174240.GA5632@nevyn.them.org>
2006-05-25 22:49 ` Daniel Jacobowitz
2006-05-31 15:33 ` Daniel Jacobowitz
2006-06-23 6:03 ` Alan Modra
2006-07-17 16:21 ` Jakub Jelinek
2006-07-17 16:31 ` Daniel Jacobowitz
2006-07-17 20:07 ` 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=200607172002.k6HK2t4X025897@greed.delorie.com \
--to=dj@redhat.com \
--cc=binutils@sourceware.org \
--cc=drow@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=jakub@redhat.com \
--cc=rda@sourceware.org \
--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).