From: Mike Stump <mikestump@comcast.net>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, java-patches@gcc.gnu.org,
bonzini@gnu.org, dj@redhat.com, neroden@gcc.gnu.org,
aoliva@redhat.com, Ralf.Wildenhues@gmx.de
Subject: Re: Toplevel cleanup: split out libgcj disabling
Date: Wed, 27 Apr 2011 17:31:00 -0000 [thread overview]
Message-ID: <23898344-B2C3-469C-A19C-9E16B3360528@comcast.net> (raw)
In-Reply-To: <Pine.LNX.4.64.1104271547150.13750@digraph.polyomino.org.uk>
On Apr 27, 2011, at 8:50 AM, Joseph S. Myers wrote:
> Continuing the toplevel cleanups separating the cases disabling
> different subdirectories
I've audited the two patches for darwin and they seem safe. Took me a second to figure out why though.
next prev parent reply other threads:[~2011-04-27 17:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 15:50 Joseph S. Myers
2011-04-27 16:34 ` Toplevel cleanup: disable Java when libffi not supported Joseph S. Myers
2011-04-27 16:38 ` Andrew Haley
2011-04-28 6:34 ` Paolo Bonzini
2011-04-28 13:40 ` Joseph S. Myers
2011-04-28 16:18 ` Toplevel cleanup: reduce libgcj disabling Joseph S. Myers
2011-04-28 16:41 ` Paolo Bonzini
2011-04-29 16:26 ` Toplevel cleanup: disable Java when libffi not supported Tom Tromey
2011-04-29 22:57 ` Joseph S. Myers
2011-05-03 15:16 ` Tom Tromey
2011-04-27 17:31 ` Mike Stump [this message]
2011-04-28 6:31 ` Toplevel cleanup: split out libgcj disabling Paolo Bonzini
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=23898344-B2C3-469C-A19C-9E16B3360528@comcast.net \
--to=mikestump@comcast.net \
--cc=Ralf.Wildenhues@gmx.de \
--cc=aoliva@redhat.com \
--cc=bonzini@gnu.org \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=java-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=neroden@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).