From: DJ Delorie <dj@redhat.com>
To: drow@false.org
Cc: joseph@codesourcery.com, gdb-patches@sourceware.org,
gcc-patches@gcc.gnu.org
Subject: Re: GDB/libiberty support for IBM long double
Date: Wed, 07 Nov 2007 23:26:00 -0000 [thread overview]
Message-ID: <200711072322.lA7NMYDI007884@greed.delorie.com> (raw)
In-Reply-To: <20071107224308.GA1438@caradoc.them.org> (message from Daniel Jacobowitz on Wed, 7 Nov 2007 17:43:08 -0500)
> DJ, are the libiberty and include bits of this OK now?
I pre-approved them with those changes already.
next prev parent reply other threads:[~2007-11-07 23:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 3:03 Joseph S. Myers
2007-10-26 3:04 ` DJ Delorie
2007-10-27 23:12 ` Joseph S. Myers
2007-11-07 22:43 ` Daniel Jacobowitz
2007-11-07 23:26 ` DJ Delorie [this message]
2007-11-09 1:26 ` Ulrich Weigand
2007-11-13 6:48 ` Joseph S. Myers
2007-11-13 14:35 ` Ulrich Weigand
2007-11-13 15:42 ` Joseph S. Myers
2007-11-13 15:58 ` DJ Delorie
2007-11-13 20:06 ` Ulrich Weigand
2007-10-26 9:25 ` Mark Kettenis
2007-10-26 15:43 ` Joseph S. Myers
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=200711072322.lA7NMYDI007884@greed.delorie.com \
--to=dj@redhat.com \
--cc=drow@false.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=joseph@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).