From: Eric Botcazou <ebotcazou@adacore.com>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc-patches@gcc.gnu.org,
"libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
GCJ-patches <java-patches@gcc.gnu.org>
Subject: Re: [patch] Clean up detection of SJLJ exceptions in target libraries
Date: Wed, 13 May 2015 17:53:00 -0000 [thread overview]
Message-ID: <1667322.0IaDKIYS9R@polaris> (raw)
In-Reply-To: <CAKOQZ8x9U1y_QG5PK8uiJ=7Zr1KeEjOdWCzDmOqPJ94eQHuRRQ@mail.gmail.com>
> The libgo parts are fine, but since libgo is mirrored from an external
> repository I'll commit those parts myself.
Thanks!
> I assume I can go ahead and commit them now?
Yes, you can, the libgo bits are independent.
--
Eric Botcazou
prev parent reply other threads:[~2015-05-13 17:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 16:45 Eric Botcazou
2015-05-12 20:26 ` Jeff Law
2015-05-13 7:53 ` Eric Botcazou
2015-05-13 7:55 ` Andrew Pinski
2015-05-13 10:37 ` Jonathan Wakely
2015-05-13 12:11 ` Matt Breedlove
2015-05-13 16:11 ` Eric Botcazou
2015-05-13 16:26 ` Ian Lance Taylor
2015-05-13 17:53 ` Eric Botcazou [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=1667322.0IaDKIYS9R@polaris \
--to=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@google.com \
--cc=java-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
/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).